From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: pciback Date: Thu, 14 Dec 2006 08:35:58 +0000 Message-ID: References: <13426df10612131919t2a59f6ablb7528d88dbd0bfda@mail.gmail.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <13426df10612131919t2a59f6ablb7528d88dbd0bfda@mail.gmail.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: ron minnich , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org On 14/12/06 3:19 am, "ron minnich" 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