WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

Re: [Xen-devel] [RFC][PATCH 4/6] HVM PCI Passthrough (non-IOMMU)

To: "Tian, Kevin" <kevin.tian@xxxxxxxxx>, Guy Zana <guy@xxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] [RFC][PATCH 4/6] HVM PCI Passthrough (non-IOMMU)
From: Keir Fraser <Keir.Fraser@xxxxxxxxxxxx>
Date: Fri, 01 Jun 2007 09:22:21 +0100
Delivery-date: Fri, 01 Jun 2007 01:18:19 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <D470B4E54465E3469E2ABBC5AFAC390F013B1EBF@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acej2E1juVhMSFpbRnuzdID01/diyQAG1qiQAAyUXwI=
Thread-topic: [Xen-devel] [RFC][PATCH 4/6] HVM PCI Passthrough (non-IOMMU)
User-agent: Microsoft-Entourage/11.3.3.061214
On 1/6/07 03:45, "Tian, Kevin" <kevin.tian@xxxxxxxxx> wrote:

> My knowledge about 'boot interrupt' issue is related to EOI
> masked RTE entry on some chipset, and not sure the influence of
> polarity change. Then ioapic_acknew may be replaced by this way
> which is more efficient if working. Two times interrupt may be still
> better than EOI-in-end which blocks other pending interrupt, and the
> 2nd interrupt should be quick since only xen internal status is touched.

That's a dubious claim imo. Doubling the rate of interrupts for high-rate
devices is not going to be a performance win, particularly if the interrupts
often require a VMEXIT/VMENTRY round trip. However, ioapic_ack=new is kind
of gross, so if we were confident that high-rate devices were able to use
MSIs, or if I can be convinced that the VT-d approach of re-vectoring the
RTE is robust and applicable to any generic IOAPIC, then I would be quite
happy to kill off ioapic_ack=new.

 -- Keir



_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel

<Prev in Thread] Current Thread [Next in Thread>