From: Paolo Bonzini <pbonzini@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Mathias Krause <minipli@grsecurity.net>
Subject: Re: [PATCH] KVM: nVMX: Emulate NOPs in L2, and PAUSE if it's not intercepted
Date: Tue, 11 Apr 2023 08:37:07 +0200 [thread overview]
Message-ID: <431136bf-2e49-fbef-457d-1145c1a59fac@redhat.com> (raw)
In-Reply-To: <20230405002359.418138-1-seanjc@google.com>
On 4/5/23 02:23, Sean Christopherson wrote:
> Extend VMX's nested intercept logic for emulated instructions to handle
> "pause" interception, in quotes because KVM's emulator doesn't filter out
> NOPs when checking for nested intercepts. Failure to allow emulation of
> NOPs results in KVM injecting a #UD into L2 on any NOP that collides with
> the emulator's definition of PAUSE, i.e. on all single-byte NOPs.
>
> For PAUSE itself, honor L1's PAUSE-exiting control, but ignore PLE to
> avoid unnecessarily injecting a #UD into L2. Per the SDM, the first
> execution of PAUSE after VM-Entry is treated as the beginning of a new
> loop, i.e. will never trigger a PLE VM-Exit, and so L1 can't expect any
> given execution of PAUSE to deterministically exit.
>
> ... the processor considers this execution to be the first execution of
> PAUSE in a loop. (It also does so for the first execution of PAUSE at
> CPL 0 after VM entry.)
>
> All that said, the PLE side of things is currently a moot point, as KVM
> doesn't expose PLE to L1.
>
> Note, vmx_check_intercept() is still wildly broken when L1 wants to
> intercept an instruction, as KVM injects a #UD instead of synthesizing a
> nested VM-Exit. That issue extends far beyond NOP/PAUSE and needs far
> more effort to fix, i.e. is a problem for the future.
>
> Fixes: 07721feee46b ("KVM: nVMX: Don't emulate instructions in guest mode")
> Cc: Mathias Krause <minipli@grsecurity.net>
> Cc: stable@vger.kernel.org
> Signed-off-by: Sean Christopherson <seanjc@google.com>
> ---
> arch/x86/kvm/vmx/vmx.c | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
>
> diff --git a/arch/x86/kvm/vmx/vmx.c b/arch/x86/kvm/vmx/vmx.c
> index 9ae4044f076f..1e560457bf9a 100644
> --- a/arch/x86/kvm/vmx/vmx.c
> +++ b/arch/x86/kvm/vmx/vmx.c
> @@ -7898,6 +7898,21 @@ static int vmx_check_intercept(struct kvm_vcpu *vcpu,
> /* FIXME: produce nested vmexit and return X86EMUL_INTERCEPTED. */
> break;
>
> + case x86_intercept_pause:
> + /*
> + * PAUSE is a single-byte NOP with a REPE prefix, i.e. collides
> + * with vanilla NOPs in the emulator. Apply the interception
> + * check only to actual PAUSE instructions. Don't check
> + * PAUSE-loop-exiting, software can't expect a given PAUSE to
> + * exit, i.e. KVM is within its rights to allow L2 to execute
> + * the PAUSE.
> + */
> + if ((info->rep_prefix != REPE_PREFIX) ||
> + !nested_cpu_has2(vmcs12, CPU_BASED_PAUSE_EXITING))
> + return X86EMUL_CONTINUE;
> +
> + break;
> +
> /* TODO: check more intercepts... */
> default:
> break;
>
> base-commit: 27d6845d258b67f4eb3debe062b7dacc67e0c393
Reviewed-by: Paolo Bonzini <pbonzini@redhat.com>
Would you like me to apply this for 6.3?
Paolo
next prev parent reply other threads:[~2023-04-11 6:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 0:23 Sean Christopherson
2023-04-10 23:31 ` Sean Christopherson
2023-04-11 6:37 ` Paolo Bonzini [this message]
2023-04-11 16:07 ` Sean Christopherson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=431136bf-2e49-fbef-457d-1145c1a59fac@redhat.com \
--to=pbonzini@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=minipli@grsecurity.net \
--cc=seanjc@google.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®