Reference in a new issue

Blame

Copy permalink

Reference in a new issue

Copy permalink

Paolo Bonzini 28b0107f54 x86: kvm: use alternatives for VMCALL vs. VMMCALL if kernel text is read-only ... commit c1118b3602 upstream. 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> Signed-off-by: Chris J Arges <chris.j.arges@canonical.com> Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>		History 2014-12-06 15:55:40 -08:00
..
asm	x86: kvm: use alternatives for VMCALL vs. VMMCALL if kernel text is read-only	2014-12-06 15:55:40 -08:00
uapi/asm	kvm: vmx: handle invvpid vm exit gracefully	2014-11-14 08:59:55 -08:00