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

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Re: [PATCH] AMD IOMMU: Hanlde sibling device assignment correctly
From: David Edmondson <dme@xxxxxxx>
Date: Wed, 07 May 2008 14:52:08 +0100
Cc: Wei Wang2 <wei.wang2@xxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Wed, 07 May 2008 06:53:04 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <C4476893.205CC%keir.fraser@xxxxxxxxxxxxx>
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: <C4476893.205CC%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx

On 7 May 2008, at 2:09pm, Keir Fraser wrote:
On 7/5/08 11:17, "Wei Wang2" <wei.wang2@xxxxxxx> wrote:

This patch seems to do more than you suggest, for example adding an extra
iommu hook into setup.c for dom0.
My idea is to let dom0 construct pci device list according to
configuration of pciback.hide=(). If a device is not hidden from dom0, it might be in use by dom0, then it could be dangerous to assign any of its siblings to other passthru domain. It is not very clean to hook into
setup.c but I failed to find any better way to this  :(

I might be confused about how this works. Are you saying that if a domU gets a device passed-thru that is a sibling of a dom0-driven device, then dom0
will mistakenly have its device's DMAs remapped according to the domU
mappings that get set up?

If a device is behind a PCI-E to PCI bridge there are cases where transactions from the device are re-written by the bridge to use the requestor id of the bridge. Given that the requestor id is the token used by the IOMMU to determine the domain which initiated the IO, this effectively means that devices behind a PCI-E to PCI bridge are not divisible - they (and the bridge) must all be assigned to the same domain.

At least, that's my understanding :-/


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