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

Re: [Xen-devel] pciback

  • To: ron minnich <rminnich@xxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • From: Keir Fraser <keir@xxxxxxxxxxxxx>
  • Date: Thu, 14 Dec 2006 08:35:58 +0000
  • Delivery-date: Thu, 14 Dec 2006 00:36:25 -0800
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AccfWuCoHwJxrItOEduXcgANk04WTA==
  • Thread-topic: [Xen-devel] pciback

On 14/12/06 3:19 am, "ron minnich" <rminnich@xxxxxxxxx> wrote:

> 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.

How are you driving pciback? Xend-based toolstack in Linux dom0? Have you
got as far as trying to access the PCI device from your plan9 domU yet?

 -- Keir

Xen-devel mailing list



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