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/
Home Products Support Community News


[Xen-devel] pv_ops reassigndev for pci passthrough

To: xen-devel@xxxxxxxxxxxxxxxxxxx, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] pv_ops reassigndev for pci passthrough
From: Michael D Labriola <mlabriol@xxxxxxxx>
Date: Wed, 23 Dec 2009 12:42:13 -0500
Delivery-date: Wed, 23 Dec 2009 09:42:36 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
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/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
What ever happened to the reassigndev= kernel arg?  I read through a bunch 
of emails way back when that was trying to get upstreamed... basically 
Greg KH didn't like using the PCI addresses as arguments.  Did that get 
addressed in later 2.6.18 trees?  Am I correct in assuming that 
reassigndev= and/or its replacement is not in xen/master yet?

I've got PCI devices passed into domUs on a couple different boxes using 
xen-pciback.hide, but it only works if the PCI device is page-aligned.


Michael D Labriola
Electric Boat
401-848-8871 (office)
401-316-9844 (cell)

Xen-devel mailing list