handle_wrmsr behavior under kvm-83
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
Quoted 2 lines · Steven Stovall
When looking at the
EXIT_REASON_MSR_WRITEevents that triggerhandle_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