From: Keir Fraser <keir@xensource.com>
To: ron minnich <rminnich@gmail.com>, xen-devel@lists.xensource.com
Subject: Re: pciback
Date: Thu, 14 Dec 2006 08:35:58 +0000 [thread overview]
Message-ID: <C1A6BD6E.5D55%keir@xensource.com> (raw)
In-Reply-To: <13426df10612131919t2a59f6ablb7528d88dbd0bfda@mail.gmail.com>
On 14/12/06 3:19 am, "ron minnich" <rminnich@gmail.com> 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
next prev parent reply other threads:[~2006-12-14 8:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-14 3:19 pciback ron minnich
2006-12-14 8:35 ` Keir Fraser [this message]
2006-12-14 15:20 ` pciback ron minnich
2006-12-14 15:53 ` pciback Ian Campbell
2006-12-14 20:26 ` pciback ron minnich
2006-12-14 22:28 ` pciback Ian Campbell
2006-12-14 22:55 ` pciback ron minnich
2006-12-15 7:15 ` pciback Ian Campbell
2006-12-15 16:50 ` pciback ron minnich
2006-12-14 21:43 ` pciback ron minnich
-- strict thread matches above, loose matches on Subject: below --
2012-03-19 2:25 pciback Teo En Ming (Zhang Enming)
2012-03-19 2:29 ` pciback Fajar A. Nugraha
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C1A6BD6E.5D55%keir@xensource.com \
--to=keir@xensource.com \
--cc=rminnich@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.