From: Jan Kiszka <jan.kiszka@web.de>
To: Gleb Natapov <gleb@redhat.com>, Marcelo Tosatti <mtosatti@redhat.com>
Cc: kvm <kvm@vger.kernel.org>, Paolo Bonzini <pbonzini@redhat.com>,
Nadav Har'El <nyh@math.technion.ac.il>
Subject: Re: [PATCH v2 0/5] KVM: nVMX: Make direct IRQ/NMI injection work
Date: Sat, 16 Mar 2013 11:42:52 +0100 [thread overview]
Message-ID: <51444CAC.1030305@web.de> (raw)
In-Reply-To: <cover.1363429383.git.jan.kiszka@web.de>
[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]
On 2013-03-16 11:23, Jan Kiszka wrote:
> Version 2 both takes review comments into account, reorders some patches
> that have dependencies and also addresses new findings regarding NMI
> injections. Fixes for vmx_interrupt_allowed and vmx_nmi_allowed were
> split up as they turn out to be more different to each other and are
> independent anyway. Finally there was still a bug in the handling of
> EXIT_REASON_NMI_WINDOW - the wrong condition was checked.
>
> Applies on top of 'queue'.
>
> Jan Kiszka (5):
> KVM: nVMX: Fix injection of PENDING_INTERRUPT and NMI_WINDOW exits to
> L1
> KVM: nVMX: Rework event injection and recovery
> KVM: VMX: Move vmx_nmi_allowed after vmx_set_nmi_mask
> KVM: nVMX: Fix conditions for interrupt injection
> KVM: nVMX: Fix conditions for NMI injection
>
> arch/x86/kvm/vmx.c | 210 ++++++++++++++++++++++++++++++++++++++--------------
> 1 files changed, 154 insertions(+), 56 deletions(-)
>
BTW, I added nested virtualization test cases for KVM to our GSoC
project list. Anyone who want to join me in mentoring is very welcome.
I'm not too optimistic if we can attract a good student for this, it's
quite tricky topic, but it's also a thrilling one IMO.
Jan
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 263 bytes --]
prev parent reply other threads:[~2013-03-16 10:43 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-16 10:23 [PATCH v2 0/5] KVM: nVMX: Make direct IRQ/NMI injection work Jan Kiszka
2013-03-16 10:23 ` [PATCH v2 1/5] KVM: nVMX: Fix injection of PENDING_INTERRUPT and NMI_WINDOW exits to L1 Jan Kiszka
2013-03-17 13:47 ` Gleb Natapov
2013-03-16 10:23 ` [PATCH v2 2/5] KVM: nVMX: Rework event injection and recovery Jan Kiszka
2013-03-17 13:45 ` Gleb Natapov
2013-03-17 15:02 ` Jan Kiszka
2013-03-17 15:14 ` Gleb Natapov
2013-03-17 15:17 ` Jan Kiszka
2013-03-17 15:19 ` Gleb Natapov
2013-03-16 10:23 ` [PATCH v2 3/5] KVM: VMX: Move vmx_nmi_allowed after vmx_set_nmi_mask Jan Kiszka
2013-03-16 10:23 ` [PATCH v2 4/5] KVM: nVMX: Fix conditions for interrupt injection Jan Kiszka
2013-03-16 10:23 ` [PATCH v2 5/5] KVM: nVMX: Fix conditions for NMI injection Jan Kiszka
2013-03-16 10:42 ` Jan Kiszka [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=51444CAC.1030305@web.de \
--to=jan.kiszka@web.de \
--cc=gleb@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=nyh@math.technion.ac.il \
--cc=pbonzini@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.