From: Maxim Levitsky <mlevitsk@redhat.com>
To: Sean Christopherson <seanjc@google.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
Santosh Shukla <santosh.shukla@amd.com>
Subject: Re: [PATCH] KVM: SVM: Don't intercept IRET when injecting NMI and vNMI is enabled
Date: Tue, 10 Oct 2023 19:06:25 +0300 [thread overview]
Message-ID: <1ca607bcb4931b7f5e14e6c064264d86e58fd3ce.camel@redhat.com> (raw)
In-Reply-To: <ZSVju-lerDbxwamL@google.com>
У вт, 2023-10-10 у 07:46 -0700, Sean Christopherson пише:
> On Tue, Oct 10, 2023, Maxim Levitsky wrote:
> > У пн, 2023-10-09 у 14:29 -0700, Sean Christopherson пише:
> > > Note, per the APM, hardware sets the BLOCKING flag when software directly
> > > directly injects an NMI:
> > >
> > > If Event Injection is used to inject an NMI when NMI Virtualization is
> > > enabled, VMRUN sets V_NMI_MASK in the guest state.
> >
> > I think that this comment is not needed in the commit message. It describes
> > a different unrelated concern and can be put somewhere in the code but
> > not in the commit message.
>
> I strongly disagree, this blurb in the APM directly affects the patch. If hardware
> didn't set V_NMI_MASK, then the patch would need to be at least this:
I don't see how 'the blurb in the APM' relates to the removal of the
IRET intercept, which is what this patch is about.
If the hardware was not to set the V_NMI_BLOCKING_MASK during EVENTINJ NMI injection,
we would have had a bigger problem, a problem which would have to be addressed
before this patch, because kvm reads back the V_NMI_BLOCKING_MASK
(see: svm_get_nmi_mask()) to check if NMI is blocked, something that
has no relation to the IRET interception.
Best regards,
Maxim Levtsky
>
> --
> diff --git a/arch/x86/kvm/svm/svm.c b/arch/x86/kvm/svm/svm.c
> index b7472ad183b9..d34ee3b8293e 100644
> --- a/arch/x86/kvm/svm/svm.c
> +++ b/arch/x86/kvm/svm/svm.c
> @@ -3569,8 +3569,12 @@ static void svm_inject_nmi(struct kvm_vcpu *vcpu)
> if (svm->nmi_l1_to_l2)
> return;
>
> - svm->nmi_masked = true;
> - svm_set_iret_intercept(svm);
> + if (is_vnmi_enabled(svm)) {
> + svm->vmcb->control.int_ctl |= V_NMI_BLOCKING_MASK;
> + } else {
> + svm->nmi_masked = true;
> + svm_set_iret_intercept(svm);
> + }
> ++vcpu->stat.nmi_injections;
> }
>
>
> base-commit: 86701e115030e020a052216baa942e8547e0b487
next prev parent reply other threads:[~2023-10-10 16:09 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-09 21:29 Sean Christopherson
2023-10-10 12:03 ` Maxim Levitsky
2023-10-10 14:46 ` Sean Christopherson
2023-10-10 16:06 ` Maxim Levitsky [this message]
2023-10-10 17:50 ` Sean Christopherson
2023-10-14 10:16 ` Santosh Shukla
2023-10-14 14:49 ` Santosh Shukla
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=1ca607bcb4931b7f5e14e6c064264d86e58fd3ce.camel@redhat.com \
--to=mlevitsk@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pbonzini@redhat.com \
--cc=santosh.shukla@amd.com \
--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®