diff options
| author | Joao Martins <joao.m.martins@oracle.com> | 2018-06-13 06:10:37 -0400 |
|---|---|---|
| committer | David Woodhouse <dwmw@amazon.co.uk> | 2021-02-04 13:58:34 +0000 |
| commit | 1232f8e6c9d15e6d043452f5d8895fcebc6a1ff2 (patch) | |
| tree | f177ebe4451a0a7206312e7fb48dc22ac9af59e8 /certs | |
| parent | a2855afc7ee88475e8feb16840b23f787bfc994d (diff) | |
| download | linux-1232f8e6c9d15e6d043452f5d8895fcebc6a1ff2.tar.bz2 | |
KVM: x86/xen: fix Xen hypercall page msr handling
Xen usually places its MSR at 0x40000000 or 0x40000200 depending on
whether it is running in viridian mode or not. Note that this is not
ABI guaranteed, so it is possible for Xen to advertise the MSR some
place else.
Given the way xen_hvm_config() is handled, if the former address is
selected, this will conflict with Hyper-V's MSR
(HV_X64_MSR_GUEST_OS_ID) which unconditionally uses the same address.
Given that the MSR location is arbitrary, move the xen_hvm_config()
handling to the top of kvm_set_msr_common() before falling through.
Signed-off-by: Joao Martins <joao.m.martins@oracle.com>
Signed-off-by: David Woodhouse <dwmw@amazon.co.uk>
Diffstat (limited to 'certs')
0 files changed, 0 insertions, 0 deletions