diff options
| author | Paolo Bonzini <pbonzini@redhat.com> | 2014-09-22 11:17:48 (GMT) |
|---|---|---|
| committer | Paolo Bonzini <pbonzini@redhat.com> | 2014-09-24 12:07:57 (GMT) |
| commit | c1118b3602c2329671ad5ec8bdf8e374323d6343 (patch) | |
| tree | 57dce6397f2dbf19701fa1a7671abcde453e170b /virt | |
| parent | 81760dccf8d1fe5b128b58736fe3f56a566133cb (diff) | |
| download | linux-c1118b3602c2329671ad5ec8bdf8e374323d6343.tar.xz | |
x86: kvm: use alternatives for VMCALL vs. VMMCALL if kernel text is read-only
On x86_64, kernel text mappings are mapped read-only with CONFIG_DEBUG_RODATA.
In that case, KVM will fail to patch VMCALL instructions to VMMCALL
as required on AMD processors.
The failure mode is currently a divide-by-zero exception, which obviously
is a KVM bug that has to be fixed. However, picking the right instruction
between VMCALL and VMMCALL will be faster and will help if you cannot upgrade
the hypervisor.
Reported-by: Chris Webb <chris@arachsys.com>
Tested-by: Chris Webb <chris@arachsys.com>
Cc: Thomas Gleixner <tglx@linutronix.de>
Cc: Ingo Molnar <mingo@redhat.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>
Cc: x86@kernel.org
Acked-by: Borislav Petkov <bp@suse.de>
Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions