From: Gleb Natapov <gleb@redhat.com>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Marcelo Tosatti <mtosatti@redhat.com>, kvm <kvm@vger.kernel.org>,
Paolo Bonzini <pbonzini@redhat.com>,
"Nadav Har'El" <nyh@math.technion.ac.il>
Subject: Re: [PATCH v4 0/6] KVM: nVMX: Make direct IRQ/NMI injection work
Date: Sun, 14 Apr 2013 18:34:19 +0300 [thread overview]
Message-ID: <20130414153419.GU17919@redhat.com> (raw)
In-Reply-To: <cover.1365934368.git.jan.kiszka@web.de>
On Sun, Apr 14, 2013 at 12:12:44PM +0200, Jan Kiszka wrote:
> Changes in this version:
> - reworked patch 2, 4 and 5 according to review
> - restored clearing of vm_entry_intr_info_field
> - no longer read idt_vectoring_info_field from VMCS
> - removed check of idt_vectoring_info_field on vmx_nmi_allowed/
> vmx_interrupt_allowed
> - added optimization patch 6
>
Applied everything except 3 and 5. Thanks.
> Jan Kiszka (6):
> 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
> KVM: nVMX: Avoid reading VM_EXIT_INTR_ERROR_CODE needlessly on nested
> exits
>
> arch/x86/kvm/vmx.c | 182 ++++++++++++++++++++++++++++++++++-----------------
> 1 files changed, 121 insertions(+), 61 deletions(-)
>
> --
> 1.7.3.4
--
Gleb.
prev parent reply other threads:[~2013-04-14 15:34 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-14 10:12 [PATCH v4 0/6] KVM: nVMX: Make direct IRQ/NMI injection work Jan Kiszka
2013-04-14 10:12 ` [PATCH v4 1/6] KVM: nVMX: Fix injection of PENDING_INTERRUPT and NMI_WINDOW exits to L1 Jan Kiszka
2013-04-14 10:12 ` [PATCH v4 2/6] KVM: nVMX: Rework event injection and recovery Jan Kiszka
2013-04-14 10:12 ` [PATCH v4 3/6] KVM: VMX: Move vmx_nmi_allowed after vmx_set_nmi_mask Jan Kiszka
2013-04-14 10:12 ` [PATCH v4 4/6] KVM: nVMX: Fix conditions for interrupt injection Jan Kiszka
2013-04-14 10:12 ` [PATCH v4 5/6] KVM: nVMX: Fix conditions for NMI injection Jan Kiszka
2013-04-14 15:23 ` Gleb Natapov
2013-04-14 15:53 ` Jan Kiszka
2013-04-14 16:18 ` Gleb Natapov
2013-04-14 16:35 ` Jan Kiszka
2013-04-14 16:43 ` Gleb Natapov
2013-04-14 19:04 ` [PATCH v5 " Jan Kiszka
2013-04-15 15:42 ` Gleb Natapov
2013-04-22 8:11 ` Gleb Natapov
2013-04-14 10:12 ` [PATCH v4 6/6] KVM: nVMX: Avoid reading VM_EXIT_INTR_ERROR_CODE needlessly on nested exits Jan Kiszka
2013-04-14 15:34 ` Gleb Natapov [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=20130414153419.GU17919@redhat.com \
--to=gleb@redhat.com \
--cc=jan.kiszka@web.de \
--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.