Skip to contentSkip to conversation

handle_wrmsr behavior under kvm-83

DISCUSSION Steven Stovall 2 participants 2 messages Jan 29, 2009 – Feb 2, 2009 1 message not in the archive KVM

lore
Share & tools
lore
#1 lore raw
In reply to a message not in the archive

When looking at the EXIT_REASON_MSR_WRITE events that trigger handle_wrmsr() invocations, why do I only seem to see indices for MSR_MTRRfix* (0x250 - 0x2ff)? This behavior seems to have changed since kvm-60, where I would see for example SYSENTER MSR writes.

Steven

#2 lore raw
Quoted 2 lines · Steven Stovall

When looking at the EXIT_REASON_MSR_WRITE events that trigger handle_wrmsr() invocations, why do I only seem to see indices for MSR_MTRRfix* (0x250 - 0x2ff)? This behavior seems to have changed since kvm-60, where I would see for example SYSENTER MSR writes.

In vmx_init():

   vmx_disable_intercept_for_msr(vmx_msr_bitmap, MSR_FS_BASE);
   vmx_disable_intercept_for_msr(vmx_msr_bitmap, MSR_GS_BASE);
   vmx_disable_intercept_for_msr(vmx_msr_bitmap, MSR_IA32_SYSENTER_CS);
   vmx_disable_intercept_for_msr(vmx_msr_bitmap, MSR_IA32_SYSENTER_ESP);
   vmx_disable_intercept_for_msr(vmx_msr_bitmap, MSR_IA32_SYSENTER_EIP);
Signature · 1 line
error compiling committee.c: too many arguments to function