From: "Michael S. Tsirkin" <mst@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: kvm@vger.kernel.org, avi@redhat.com
Subject: Re: [PATCH corrected RFC] uio: add generic driver for PCI 2.3 devices
Date: Thu, 9 Jul 2009 21:12:58 +0300 [thread overview]
Message-ID: <20090709181258.GA4340@redhat.com> (raw)
In-Reply-To: <4A5604B3.2090508@codemonkey.ws>
On Thu, Jul 09, 2009 at 09:54:43AM -0500, Anthony Liguori wrote:
> I know it's not strictly needed for PCI pass through, but it would be
> useful to register the IO regions via UIO. The userspace implementation
> would then use UIO strictly instead of poking the sysfs pci info
> directly. I think that ends up being cleaner.
Hmm, this is good for specific drivers, but for a generic one like qemu,
still need sysfs to figure out the size at least, and
we need config accesses which uio does not support now.
And if you use libpci as qemu does now, this interface will likely
go unused. So .. there does not seem to be much point at the moment.
My idea is, let's start with a minimal interface, longer term
let's see if we can add config access, mmap and other stuff like eventfd.
Makes sense?
--
MST
next prev parent reply other threads:[~2009-07-09 18:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-09 11:48 [PATCH corrected RFC] uio: add generic driver for PCI 2.3 devices Michael S. Tsirkin
2009-07-09 14:54 ` Anthony Liguori
2009-07-09 18:12 ` Michael S. Tsirkin [this message]
2009-07-09 20:14 ` Anthony Liguori
2009-07-09 20:21 ` Michael S. Tsirkin
2009-07-10 2:22 ` Chris Wright
2009-07-12 6:17 ` Avi Kivity
2009-07-10 2:19 ` Chris Wright
2009-07-10 13:56 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2009-07-09 18:13 Michael S. Tsirkin
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=20090709181258.GA4340@redhat.com \
--to=mst@redhat.com \
--cc=anthony@codemonkey.ws \
--cc=avi@redhat.com \
--cc=kvm@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox