From: Paolo Bonzini <pbonzini@redhat.com>
To: Cathy Avery <cavery@redhat.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: vkuznets@redhat.com, wei.huang2@amd.com
Subject: Re: [PATCH 0/2] KVM: SVM: Implement check_nested_events for NMI
Date: Thu, 23 Apr 2020 15:43:10 +0200 [thread overview]
Message-ID: <8c3f87de-525a-63d5-0134-606250d8c945@redhat.com> (raw)
In-Reply-To: <20200414201107.22952-1-cavery@redhat.com>
On 14/04/20 22:11, Cathy Avery wrote:
> Moved nested NMI exit to new check_nested_events.
> The second patch fixes the NMI pending race condition that now occurs.
>
> Cathy Avery (2):
> KVM: SVM: Implement check_nested_events for NMI
> KVM: x86: check_nested_events if there is an injectable NMI
>
> arch/x86/kvm/svm/nested.c | 21 +++++++++++++++++++++
> arch/x86/kvm/svm/svm.c | 2 +-
> arch/x86/kvm/svm/svm.h | 15 ---------------
> arch/x86/kvm/x86.c | 15 +++++++++++----
> 4 files changed, 33 insertions(+), 20 deletions(-)
>
Thanks, I've integrated this in Sean's event reinjection series and will
post soon my own take on both.
Paolo
prev parent reply other threads:[~2020-04-23 13:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 20:11 [PATCH 0/2] KVM: SVM: Implement check_nested_events for NMI Cathy Avery
2020-04-14 20:11 ` [PATCH 1/2] " Cathy Avery
2020-04-14 20:11 ` [PATCH 2/2] KVM: x86: check_nested_events if there is an injectable NMI Cathy Avery
2020-04-23 14:42 ` Sean Christopherson
2020-04-23 15:10 ` Paolo Bonzini
2020-04-23 15:35 ` Sean Christopherson
2020-04-23 15:43 ` Paolo Bonzini
2020-04-23 18:32 ` Paolo Bonzini
2020-04-23 15:36 ` Cathy Avery
2020-04-23 15:45 ` Paolo Bonzini
2020-04-23 18:33 ` Sean Christopherson
2020-04-23 18:47 ` Paolo Bonzini
2020-04-15 9:49 ` [PATCH 0/2] KVM: SVM: Implement check_nested_events for NMI Vitaly Kuznetsov
2020-04-15 12:45 ` Paolo Bonzini
2020-04-23 13:43 ` 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=8c3f87de-525a-63d5-0134-606250d8c945@redhat.com \
--to=pbonzini@redhat.com \
--cc=cavery@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vkuznets@redhat.com \
--cc=wei.huang2@amd.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;
as well as URLs for NNTP newsgroup(s).