From mboxrd@z Thu Jan  1 00:00:00 1970
From: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
Subject: Re: [Xenhackthon] Virtualized APIC registers - virtual
 interrupt delivery.
Date: Mon, 15 Jul 2013 10:54:33 -0400
Message-ID: <20130715145433.GA5521@phenom.dumpdata.com>
References: <alpine.DEB.2.02.1305271129510.4799@kaball.uk.xensource.com>
	<A9667DDFB95DB7438FA9D7D576C3D87E0A8723F3@SHSMSX104.ccr.corp.intel.com>
	<alpine.DEB.2.02.1305281710150.4799@kaball.uk.xensource.com>
	<A9667DDFB95DB7438FA9D7D576C3D87E0A87332D@SHSMSX104.ccr.corp.intel.com>
	<alpine.DEB.2.02.1305291100150.4799@kaball.uk.xensource.com>
	<20130603125949.GH6893@phenom.dumpdata.com>
	<alpine.DEB.2.02.1306031620490.4589@kaball.uk.xensource.com>
	<A9667DDFB95DB7438FA9D7D576C3D87E0A885EF7@SHSMSX104.ccr.corp.intel.com>
	<alpine.DEB.2.02.1306051330500.4589@kaball.uk.xensource.com>
	<A9667DDFB95DB7438FA9D7D576C3D87E0A887B4F@SHSMSX104.ccr.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <xen-devel-bounces@lists.xen.org>
Content-Disposition: inline
In-Reply-To: <A9667DDFB95DB7438FA9D7D576C3D87E0A887B4F@SHSMSX104.ccr.corp.intel.com>
List-Unsubscribe: <http://lists.xen.org/cgi-bin/mailman/options/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xen.org>
List-Help: <mailto:xen-devel-request@lists.xen.org?subject=help>
List-Subscribe: <http://lists.xen.org/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xen.org?subject=subscribe>
Sender: xen-devel-bounces@lists.xen.org
Errors-To: xen-devel-bounces@lists.xen.org
To: "Zhang, Yang Z" <yang.z.zhang@intel.com>
Cc: "Nakajima, Jun" <jun.nakajima@intel.com>, Stefano Stabellini <stefano.stabellini@eu.citrix.com>, xen-devel <xen-devel@lists.xen.org>, "keir.xen@gmail.com" <keir.xen@gmail.com>, Jan Beulich <JBeulich@suse.com>, "Zhang, Xiantao" <xiantao.zhang@intel.com>
List-Id: xen-devel@lists.xenproject.org

On Thu, Jun 06, 2013 at 03:08:07AM +0000, Zhang, Yang Z wrote:
> Stefano Stabellini wrote on 2013-06-05:
> > On Wed, 5 Jun 2013, Zhang, Yang Z wrote:
> >>>> Or just split the mechanism. Meaning use the event callback for "legacy"
> >>>> type events, and for PCI passthrough devices (where the host supports
> >>>> posted interrupts) just use the baremetal implementation.
> >>>> 
> >>>> That would entail some form of hypercall to identify whether a PCIe device
> >>>> is "posted-interrupt" candidate and if so don't use the event channel
> >>>> mechanism for it.
> >> What you mean "a PCIe device is posted-interrupt candidate"? Do you mean
> > pass-through device will use event channel currently?
> > 
> > On Linux, yes: Linux is going to remap the MSI/MSI-X onto an event
> > channel. Therefore if we want to use posted-interrupts with pass-through
> > devices we would need to disable event channel remapping for them.
> Then we must disable event channel remapping if posted interrupt is used.

When can we expect some of these patches to be posted? Thanks!
> 
> Best regards,
> Yang
> 
>