From: Avi Kivity <avi@redhat.com>
To: Marcelo Tosatti <mtosatti@redhat.com>, kvm@vger.kernel.org
Subject: [PATCH 0/6] Nonatomic interrupt injection
Date: Tue, 27 Jul 2010 16:19:34 +0300 [thread overview]
Message-ID: <1280236780-5847-1-git-send-email-avi@redhat.com> (raw)
This patchset changes interrupt injection to be done from normal process
context instead of interrupts disabled context. This is useful for real
mode interrupt injection on Intel without the current hacks (injecting as
a software interrupt of a vm86 task), reducing latencies, and later, for
allowing nested virtualization code to use kvm_read_guest()/kvm_write_guest()
instead of kmap() to access the guest vmcb/vmcs.
Seems to survive a hack that cancels every 16th entry, after injection has
already taken place.
Note: not yet ready, hangs fairly early on AMD. Seems to work well on Intel.
Please review carefully, esp. the first patch. Any missing kvm_make_request()
there may result in a hung guest.
v3: close new race between injection and entry
fix Intel real-mode injection cancellation
v2: svm support (easier than expected)
fix silly vmx warning
Avi Kivity (6):
KVM: Check for pending events before attempting injection
KVM: VMX: Split up vmx_complete_interrupts()
KVM: VMX: Move real-mode interrupt injection fixup to
vmx_complete_interrupts()
KVM: VMX: Parameterize vmx_complete_interrupts() for both exit and
entry
KVM: Non-atomic interrupt injection
KVM: VMX: Move fixup_rmode_irq() to avoid forward declaration
arch/x86/include/asm/kvm_host.h | 1 +
arch/x86/kvm/i8259.c | 1 +
arch/x86/kvm/lapic.c | 12 +++-
arch/x86/kvm/svm.c | 20 ++++++-
arch/x86/kvm/vmx.c | 116 ++++++++++++++++++++++++++------------
arch/x86/kvm/x86.c | 44 ++++++++++----
include/linux/kvm_host.h | 1 +
7 files changed, 142 insertions(+), 53 deletions(-)
next reply other threads:[~2010-07-27 13:19 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-27 13:19 Avi Kivity [this message]
2010-07-27 13:19 ` [PATCH 1/6] KVM: Check for pending events before attempting injection Avi Kivity
2010-07-28 16:21 ` Marcelo Tosatti
2010-07-28 16:31 ` Avi Kivity
2010-07-28 16:37 ` Marcelo Tosatti
2010-07-28 16:53 ` Avi Kivity
2010-07-28 17:22 ` Marcelo Tosatti
2010-07-29 8:49 ` Avi Kivity
2010-07-29 15:44 ` Marcelo Tosatti
2010-07-29 6:51 ` Gleb Natapov
2010-07-29 8:56 ` Avi Kivity
2010-07-27 13:19 ` [PATCH 2/6] KVM: VMX: Split up vmx_complete_interrupts() Avi Kivity
2010-07-27 13:19 ` [PATCH 3/6] KVM: VMX: Move real-mode interrupt injection fixup to vmx_complete_interrupts() Avi Kivity
2010-07-27 13:19 ` [PATCH 4/6] KVM: VMX: Parameterize vmx_complete_interrupts() for both exit and entry Avi Kivity
2010-07-27 13:19 ` [PATCH 5/6] KVM: Non-atomic interrupt injection Avi Kivity
2010-07-27 13:19 ` [PATCH 6/6] KVM: VMX: Move fixup_rmode_irq() to avoid forward declaration Avi Kivity
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=1280236780-5847-1-git-send-email-avi@redhat.com \
--to=avi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox