diff options
| author | Paolo Bonzini <[email protected]> | 2014-09-22 13:17:48 +0200 |
|---|---|---|
| committer | Paolo Bonzini <[email protected]> | 2014-09-24 14:07:57 +0200 |
| commit | c1118b3602c2329671ad5ec8bdf8e374323d6343 (patch) | |
| tree | 57dce6397f2dbf19701fa1a7671abcde453e170b /scripts/gdb/linux | |
| parent | 81760dccf8d1fe5b128b58736fe3f56a566133cb (diff) | |
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 <[email protected]>
Tested-by: Chris Webb <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Cc: Ingo Molnar <[email protected]>
Cc: "H. Peter Anvin" <[email protected]>
Cc: [email protected]
Acked-by: Borislav Petkov <[email protected]>
Signed-off-by: Paolo Bonzini <[email protected]>
Diffstat (limited to 'scripts/gdb/linux')
0 files changed, 0 insertions, 0 deletions