From: Paolo Bonzini <pbonzini@redhat.com>
To: linux-kernel@vger.kernel.org, kvm@vger.kernel.org
Cc: cavery@redhat.com, vkuznets@redhat.com, jan.kiszka@siemens.com,
wei.huang2@amd.com
Subject: [PATCH 0/4] KVM: nSVM: first step towards fixing event injection
Date: Thu, 5 Mar 2020 11:13:43 +0100 [thread overview]
Message-ID: <1583403227-11432-1-git-send-email-pbonzini@redhat.com> (raw)
Event injection in nSVM does not use check_nested_events, which means it
is basically broken. As a first step, this fixes interrupt injection
which is probably the most complicated case due to the interactions
with V_INTR_MASKING and the host EFLAGS.IF.
This series fixes Cathy's test case that I have sent earlier.
Paolo
Paolo Bonzini (4):
KVM: nSVM: do not change host intercepts while nested VM is running
KVM: nSVM: ignore L1 interrupt window while running L2 with
V_INTR_MASKING=1
KVM: nSVM: implement check_nested_events for interrupts
KVM: nSVM: avoid loss of pending IRQ/NMI before entering L2
arch/x86/kvm/svm.c | 172 ++++++++++++++++++++++++++++++++---------------------
1 file changed, 103 insertions(+), 69 deletions(-)
--
1.8.3.1
next reply other threads:[~2020-03-05 10:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-05 10:13 Paolo Bonzini [this message]
2020-03-05 10:13 ` [PATCH 1/4] KVM: nSVM: do not change host intercepts while nested VM is running Paolo Bonzini
2020-03-06 14:42 ` Vitaly Kuznetsov
2020-03-05 10:13 ` [PATCH 2/4] KVM: nSVM: ignore L1 interrupt window while running L2 with V_INTR_MASKING=1 Paolo Bonzini
2020-03-05 10:13 ` [PATCH 3/4] KVM: nSVM: implement check_nested_events for interrupts Paolo Bonzini
2020-03-05 23:51 ` kbuild test robot
2020-03-07 1:18 ` kbuild test robot
2020-03-05 10:13 ` [PATCH 4/4] KVM: nSVM: avoid loss of pending IRQ/NMI before entering L2 Paolo Bonzini
2020-03-05 10:46 ` Jan Kiszka
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=1583403227-11432-1-git-send-email-pbonzini@redhat.com \
--to=pbonzini@redhat.com \
--cc=cavery@redhat.com \
--cc=jan.kiszka@siemens.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
all inboxes | Powered by JetHome®