Oliver Upton f1a9761fbb KVM: x86: Allow userspace to opt out of hypercall patching ... KVM handles the VMCALL/VMMCALL instructions very strangely. Even though both of these instructions really should #UD when executed on the wrong vendor's hardware (i.e. VMCALL on SVM, VMMCALL on VMX), KVM replaces the guest's instruction with the appropriate instruction for the vendor. Nonetheless, older guest kernels without commit c1118b3602 ("x86: kvm: use alternatives for VMCALL vs. VMMCALL if kernel text is read-only") do not patch in the appropriate instruction using alternatives, likely motivating KVM's intervention. Add a quirk allowing userspace to opt out of hypercall patching. If the quirk is disabled, KVM synthesizes a #UD in the guest. Signed-off-by: Oliver Upton <oupton@google.com> Message-Id: <20220316005538.2282772-2-oupton@google.com> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>		2022-04-02 05:41:10 -04:00
..
acrn	docs: acrn: Introduce ACRN	2021-02-09 10:58:18 +01:00
kvm	KVM: x86: Allow userspace to opt out of hypercall patching	2022-04-02 05:41:10 -04:00
uml	docs: UML: user_mode_linux_howto_v2 edits	2021-10-12 14:07:35 -06:00
guest-halt-polling.rst	docs: virt: guest-halt-polling.txt convert to ReST	2020-02-12 20:10:08 +01:00
index.rst	docs: acrn: Introduce ACRN	2021-02-09 10:58:18 +01:00
ne_overview.rst	nitro_enclaves: Update documentation for Arm64 support	2021-09-14 11:11:20 +02:00
paravirt_ops.rst