public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Marcelo Tosatti <mtosatti@redhat.com>
To: Gleb Natapov <gleb@redhat.com>
Cc: Yang Zhang <yang.z.zhang@intel.com>,
	kvm@vger.kernel.org, xiantao.zhang@intel.com,
	jun.nakajima@intel.com
Subject: Re: [PATCH v10 0/7] KVM: VMX: Add Posted Interrupt supporting
Date: Tue, 16 Apr 2013 18:17:00 -0300	[thread overview]
Message-ID: <20130416211700.GB21244@amt.cnet> (raw)
In-Reply-To: <20130414094000.GH17919@redhat.com>

On Sun, Apr 14, 2013 at 12:40:00PM +0300, Gleb Natapov wrote:
> On Thu, Apr 11, 2013 at 07:25:09PM +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
> > 
> Reviewed-by: Gleb Natapov <gleb@redhat.com>

Applied, thanks.


      reply	other threads:[~2013-04-16 21:18 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-11 11:25 [PATCH v10 0/7] KVM: VMX: Add Posted Interrupt supporting Yang Zhang
2013-04-11 11:25 ` [PATCH v10 1/7] KVM: VMX: Enable acknowledge interupt on vmexit Yang Zhang
2013-04-11 11:25 ` [PATCH v10 2/7] KVM: VMX: Register a new IPI for posted interrupt Yang Zhang
2013-04-11 11:25 ` [PATCH v10 3/7] KVM: VMX: Check the posted interrupt capability Yang Zhang
2013-04-11 11:25 ` [PATCH v10 4/7] KVM: Call common update function when ioapic entry changed Yang Zhang
2013-04-11 11:25 ` [PATCH v10 5/7] KVM: Set TMR when programming ioapic entry Yang Zhang
2013-04-11 11:25 ` [PATCH v10 6/7] KVM: VMX: Add the algorithm of deliver posted interrupt Yang Zhang
2013-04-11 11:25 ` [PATCH v10 7/7] KVM: VMX: Use posted interrupt to deliver virtual interrupt Yang Zhang
2013-04-26  5:06   ` Yangminqiang
2013-04-26  5:09     ` Zhang, Yang Z
2013-04-26  9:29       ` Yangminqiang
2013-04-26 13:46         ` Nakajima, Jun
2013-05-03  2:44           ` Yangminqiang
2013-05-07  1:52             ` Zhang, Yang Z
2013-04-14  9:40 ` [PATCH v10 0/7] KVM: VMX: Add Posted Interrupt supporting Gleb Natapov
2013-04-16 21:17   ` Marcelo Tosatti [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=20130416211700.GB21244@amt.cnet \
    --to=mtosatti@redhat.com \
    --cc=gleb@redhat.com \
    --cc=jun.nakajima@intel.com \
    --cc=kvm@vger.kernel.org \
    --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