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

[Xen-devel] pciback

  • To: xen-devel@xxxxxxxxxxxxxxxxxxx
  • From: "ron minnich" <rminnich@xxxxxxxxx>
  • Date: Wed, 13 Dec 2006 20:19:28 -0700
  • Delivery-date: Wed, 13 Dec 2006 19:19:20 -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=etg9TyLml6kTd6nljrpw5OIg6t8KBafZOb7bOMqugb29QjXOD5kobzLv/udkXx6YAqRv6bzOAhkJh0qL48rNeLjEISsZA26v1CW7t+01DXzq3jwBHMUx+eC+FN9v2ubq0CMgOHn6XkAcEQ/RFX+mqY1KE+J0f3YTEnE0HDz6U1I=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>

For a given device tree in /sys, at what point should the driver
symlink say 'pciback'?

I can see from the kernel the message that pciback is trying to
'seize' the device, once I do the echo blah blah blah >
/blah/blah/blah/bind. But the driver symlink never changes.

Also the pcihide stuff doesn't seem to work either. But if I cat the
'slots' file, I do see the bus:dev.0 numbers that I am trying to tell
pciback to seize. What's the next thing I should see? Should the
devices I have seized appear in the xenstore? I kind of thought, from
reading the pci code front and back, that they should.



Xen-devel mailing list



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