From: Marcelo Tosatti Subject: Re: [PATCH v10 0/7] KVM: VMX: Add Posted Interrupt supporting Date: Tue, 16 Apr 2013 18:17:00 -0300 Message-ID: <20130416211700.GB21244@amt.cnet> References: <1365679516-13125-1-git-send-email-yang.z.zhang@intel.com> <20130414094000.GH17919@redhat.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Yang Zhang , kvm@vger.kernel.org, xiantao.zhang@intel.com, jun.nakajima@intel.com To: Gleb Natapov Return-path: Received: from mx1.redhat.com ([209.132.183.28]:28948 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S965219Ab3DPVSM (ORCPT ); Tue, 16 Apr 2013 17:18:12 -0400 Content-Disposition: inline In-Reply-To: <20130414094000.GH17919@redhat.com> Sender: kvm-owner@vger.kernel.org List-ID: 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 > > > > 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 Applied, thanks.