Fix Xen panics when trying to configure MSR intercepts in hypervisor range
(as hardware has no dedicated bitmap, since it's unconditionally intercepted).
(SVM all builds, and VMX debug builds)

Fix bogus monitored_msr() check in svm logic, which was checking for a
truncated MSR instead of the correct one.

Regarding intercepts in hypervisor range, I'm not sure if it would be preferable
to move the check higher (i.e in hvm_enable_msr_interception() to check if the
MSR is a hypervisor one, and if it is, to skip the architecture specific logic,
as it's not required at least on VMX/SVM).

Teddy Astie (3):
  vm_event: svm: Don't BUG() when enabling intercept on hypervisor MSR
  vm_event: svm: Fix incorrect monitored_msr() check
  vm_event: vmx: Allow intercepting hypervisor MSRs in debug builds

 xen/arch/x86/hvm/svm/svm.c  | 13 +++++++------
 xen/arch/x86/hvm/vmx/vmcs.c |  2 +-
 2 files changed, 8 insertions(+), 7 deletions(-)

-- 
2.55.0



-- 
Teddy Astie | Vates XCP-ng Developer

XCP-ng & Xen Orchestra - Vates solutions

web: https://vates.tech