kvm.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Paolo Bonzini <pbonzini@redhat.com>
To: "Radim Krčmář" <rkrcmar@redhat.com>, linux-kernel@vger.kernel.org
Cc: kvm@vger.kernel.org, joro@8bytes.org, stable@vger.kernel.org
Subject: Re: [PATCH] KVM: SVM: fix NMI window after iret
Date: Tue, 18 Feb 2014 10:18:21 +0100	[thread overview]
Message-ID: <5303255D.8000501@redhat.com> (raw)
In-Reply-To: <1389988362-15260-1-git-send-email-rkrcmar@redhat.com>

Il 17/01/2014 20:52, Radim Krčmář ha scritto:
> We should open NMI window right after an iret, but SVM exits before it.
> We wanted to single step using the trap flag and then open it.
> (or we could emulate the iret instead)
> We don't do it since commit 3842d135ff2 (likely), because the iret exit
> handler does not request an event, so NMI window remains closed until
> the next exit.
>
> Fix this by making KVM_REQ_EVENT request in the iret handler.
>
> Signed-off-by: Radim Krčmář <rkrcmar@redhat.com>
> ---
>  (btw. kvm-unit-tests weren't executed on SVM since Nov 2010, at least)
>
>  arch/x86/kvm/svm.c | 1 +
>  1 file changed, 1 insertion(+)
>
> diff --git a/arch/x86/kvm/svm.c b/arch/x86/kvm/svm.c
> index c7168a5..b5a735b 100644
> --- a/arch/x86/kvm/svm.c
> +++ b/arch/x86/kvm/svm.c
> @@ -2829,6 +2829,7 @@ static int iret_interception(struct vcpu_svm *svm)
>  	clr_intercept(svm, INTERCEPT_IRET);
>  	svm->vcpu.arch.hflags |= HF_IRET_MASK;
>  	svm->nmi_iret_rip = kvm_rip_read(&svm->vcpu);
> +	kvm_make_request(KVM_REQ_EVENT, &svm->vcpu);
>  	return 1;
>  }
>
>

Applying to kvm/queue, thanks.

Paolo

      parent reply	other threads:[~2014-02-18  9:18 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-17 19:52 [PATCH] KVM: SVM: fix NMI window after iret Radim Krčmář
2014-01-17 20:18 ` Greg KH
2014-01-17 20:29   ` Radim Krčmář
2014-02-18  9:18 ` Paolo Bonzini [this message]

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=5303255D.8000501@redhat.com \
    --to=pbonzini@redhat.com \
    --cc=joro@8bytes.org \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rkrcmar@redhat.com \
    --cc=stable@vger.kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).