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] [PATCH] AMD IOMMU: Hanlde sibling device assignment corr

To: Wei Wang2 <wei.wang2@xxxxxxx>
Subject: Re: [Xen-devel] [PATCH] AMD IOMMU: Hanlde sibling device assignment correctly
From: Muli Ben-Yehuda <muli@xxxxxxxxxx>
Date: Mon, 12 May 2008 10:55:08 +0300
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx, keir.fraser@xxxxxxxxxxxxx
Delivery-date: Mon, 12 May 2008 03:29:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1210154691.2841.95.camel@xxxxxxxxxxxx>
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>
References: <1210152421.2841.85.camel@xxxxxxxxxxxx> <20080507095310.GH7002@xxxxxxxxxx> <1210154691.2841.95.camel@xxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mutt/1.5.15+20070412 (2007-04-11)
On Wed, May 07, 2008 at 12:04:51PM +0200, Wei Wang2 wrote:

> I think both could be possible. If IOMMU is implemented per
> PCI-to-PCI-E bridge, then probably there will be a group of PCI
> device sharing a same PCI-E requester ID. The device table can only
> be indexed by either PCI-E requester ID or HT unit ID.

Good point. That should be a fairly rare case. It will also apply
equally well to VT-d, so this should probably be common functionality.

Cheers,
Muli

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