[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-devel] PCI pass through vs. slot

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "ron minnich" <rminnich@xxxxxxxxx>
  • Date: Tue, 5 Dec 2006 11:41:00 -0700
  • Delivery-date: Tue, 05 Dec 2006 10:40:58 -0800
  • Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=JvaxI2Emc61F6UxdviHtaAhOhiq7zc0yp+sWtNMDE67OVRugB9I9zJHDLW7EYRHMvkgolMKPbvRo7O3nL4BzBkLIgNjPwRwlMoKPcooQZb9nM6hkcMemZAMzth9nceY61bALXN+FQfMu4zqJXOYR6QPbb6yI24LTZZrsK6d6nA4=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

I am a bit confused on the PCI stuff.

PASSTHRU-- does this mean that pcifront is not needed? Or only that
the PCI is not limited as it is with slot.

In general, none of the docs are getting me anywhere with xen 3.0.3.
Example: I run this:
 echo -n 0000:2:0.1>/sys/bus/pci/drivers/pciback/new_slot
 echo -n 0000:2:0.0>/sys/bus/pci/drivers/pciback/new_slot
 echo -n bind 0000:2:0.0 > /sys/bus/pci/drivers/pciback/bind
 echo -n bind 0000:2:0.1 > /sys/bus/pci/drivers/pciback/bind

It fails in one of two ways. If there is a driver present for that
device, the driver symlink has a value, and it seems that it can not
be changed to "pciback".

if there is no driver present, there is no driver symlink, and xen
seems not be be able to set it. So the domain can not be started.

Any good writeups on PCI passthrough? I need Plan 9 to have raw access
toa device.


Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.