From: Gleb Natapov <gleb@redhat.com>
To: Yang Zhang <yang.z.zhang@intel.com>
Cc: kvm@vger.kernel.org, mtosatti@redhat.com,
xiantao.zhang@intel.com, jun.nakajima@intel.com
Subject: Re: [PATCH v9 0/7] KVM: VMX: Add Posted Interrupt supporting
Date: Wed, 10 Apr 2013 18:33:11 +0300 [thread overview]
Message-ID: <20130410153311.GK17919@redhat.com> (raw)
In-Reply-To: <1365600177-8506-1-git-send-email-yang.z.zhang@intel.com>
On Wed, Apr 10, 2013 at 09:22:50PM +0800, Yang Zhang wrote:
> From: Yang Zhang <yang.z.zhang@Intel.com>
>
> The follwoing patches are adding the Posted Interrupt supporting to KVM:
> The first patch enables the feature 'acknowledge interrupt on vmexit'.Since
> it is required by Posted interrupt, we need to enable it firstly.
>
> And the subsequent patches are adding the posted interrupt supporting:
> Posted Interrupt allows APIC interrupts to inject into guest directly
> without any vmexit.
>
> - When delivering a interrupt to guest, if target vcpu is running,
> update Posted-interrupt requests bitmap and send a notification event
> to the vcpu. Then the vcpu will handle this interrupt automatically,
> without any software involvemnt.
>
> - If target vcpu is not running or there already a notification event
> pending in the vcpu, do nothing. The interrupt will be handled by
> next vm entry
>
> Changes from v8 to v9:
> * Add tracing in PI case when deliver interrupt.
> * Scan ioapic when updating SPIV register.
Do not see it at the patch series. Have I missed it?
> * Rebase on top of KVM upstream + RTC eoi tracking patch.
>
> Changes from v7 to v8:
> * Remove unused memeber 'on' from struct pi_desc.
> * Register a dummy function to sync_pir_to_irr is apicv is disabled.
> * Minor fixup.
> * Rebase on top of KVM upstream + RTC eoi tracking patch.
>
> Yang Zhang (7):
> KVM: VMX: Enable acknowledge interupt on vmexit
> KVM: VMX: Register a new IPI for posted interrupt
> KVM: VMX: Check the posted interrupt capability
> KVM: Call common update function when ioapic entry changed.
> KVM: Set TMR when programming ioapic entry
> KVM: VMX: Add the algorithm of deliver posted interrupt
> KVM: VMX: Use posted interrupt to deliver virtual interrupt
>
> arch/ia64/kvm/lapic.h | 6 -
> arch/x86/include/asm/entry_arch.h | 4 +
> arch/x86/include/asm/hardirq.h | 3 +
> arch/x86/include/asm/hw_irq.h | 1 +
> arch/x86/include/asm/irq_vectors.h | 5 +
> arch/x86/include/asm/kvm_host.h | 3 +
> arch/x86/include/asm/vmx.h | 4 +
> arch/x86/kernel/entry_64.S | 5 +
> arch/x86/kernel/irq.c | 22 ++++
> arch/x86/kernel/irqinit.c | 4 +
> arch/x86/kvm/lapic.c | 66 ++++++++----
> arch/x86/kvm/lapic.h | 7 ++
> arch/x86/kvm/svm.c | 12 ++
> arch/x86/kvm/vmx.c | 207 +++++++++++++++++++++++++++++++-----
> arch/x86/kvm/x86.c | 19 +++-
> include/linux/kvm_host.h | 4 +-
> virt/kvm/ioapic.c | 32 ++++--
> virt/kvm/ioapic.h | 7 +-
> virt/kvm/irq_comm.c | 4 +-
> virt/kvm/kvm_main.c | 5 +-
> 20 files changed, 341 insertions(+), 79 deletions(-)
--
Gleb.
next prev parent reply other threads:[~2013-04-10 15:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-10 13:22 [PATCH v9 0/7] KVM: VMX: Add Posted Interrupt supporting Yang Zhang
2013-04-10 13:22 ` [PATCH v9 1/7] KVM: VMX: Enable acknowledge interupt on vmexit Yang Zhang
2013-04-10 13:22 ` [PATCH v9 2/7] KVM: VMX: Register a new IPI for posted interrupt Yang Zhang
2013-04-10 13:22 ` [PATCH v9 3/7] KVM: VMX: Check the posted interrupt capability Yang Zhang
2013-04-10 13:22 ` [PATCH v9 4/7] KVM: Call common update function when ioapic entry changed Yang Zhang
2013-04-10 13:22 ` [PATCH v9 5/7] KVM: Set TMR when programming ioapic entry Yang Zhang
2013-04-10 13:22 ` [PATCH v9 6/7] KVM: VMX: Add the algorithm of deliver posted interrupt Yang Zhang
2013-04-10 13:22 ` [PATCH v9 7/7] KVM: VMX: Use posted interrupt to deliver virtual interrupt Yang Zhang
2013-04-10 15:32 ` Gleb Natapov
2013-04-11 0:56 ` Zhang, Yang Z
2013-04-10 15:33 ` Gleb Natapov [this message]
2013-04-11 1:03 ` [PATCH v9 0/7] KVM: VMX: Add Posted Interrupt supporting Zhang, Yang Z
2013-04-11 5:44 ` Gleb Natapov
2013-04-11 6:05 ` Zhang, Yang Z
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=20130410153311.GK17919@redhat.com \
--to=gleb@redhat.com \
--cc=jun.nakajima@intel.com \
--cc=kvm@vger.kernel.org \
--cc=mtosatti@redhat.com \
--cc=xiantao.zhang@intel.com \
--cc=yang.z.zhang@intel.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