From: Greg KH <gregkh@suse.de>
To: Piotr Jaroszy??ski <p.jaroszynski@gmail.com>
Cc: Tom Lyon <pugs@cisco.com>,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
randy.dunlap@oracle.com, arnd@arndb.de, chrisw@sous-sol.org,
joro@8bytes.org, hjk@linutronix.de, avi@redhat.com,
alex.williamson@redhat.com, mst@redhat.com, aafabbri@cisco.com,
scofeldm@cisco.com
Subject: Re: [PATCH V3] VFIO driver: Non-privileged user level PCI drivers
Date: Tue, 20 Jul 2010 13:20:30 -0700 [thread overview]
Message-ID: <20100720202030.GC11991@suse.de> (raw)
In-Reply-To: <AANLkTin4aU9GtC8zOuQcCRAQsWb_ndih3c6URlpE4ODI@mail.gmail.com>
On Sat, Jul 17, 2010 at 10:45:23AM +0200, Piotr Jaroszy??ski wrote:
> On 16 July 2010 23:58, Tom Lyon <pugs@cisco.com> wrote:
> > The VFIO "driver" is used to allow privileged AND non-privileged processes to
> > implement user-level device drivers for any well-behaved PCI, PCI-X, and PCIe
> > devices.
>
> Thanks for working on that! I wonder whether it's possible to say what
> are the chances of it being merged to mainline and which version we
> might be talking about?
We still have a long way to go before you need to worry about what
kernel version it's going to show up in...
thanks,
greg k-h
next prev parent reply other threads:[~2010-07-20 20:24 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-07-16 21:58 [PATCH V3] VFIO driver: Non-privileged user level PCI drivers Tom Lyon
2010-07-16 21:58 ` Tom Lyon
2010-07-17 8:45 ` Piotr Jaroszyński
2010-07-20 20:20 ` Greg KH [this message]
2010-07-18 9:39 ` Michael S. Tsirkin
2010-07-19 4:56 ` Alex Williamson
2010-07-19 10:06 ` Michael S. Tsirkin
2010-07-27 22:13 ` Tom Lyon
2010-07-27 23:53 ` Michael S. Tsirkin
2010-07-28 21:14 ` Tom Lyon
2010-07-28 21:46 ` Michael S. Tsirkin
2010-07-28 21:57 ` Alex Williamson
2010-07-28 21:57 ` Michael S. Tsirkin
2010-07-28 22:13 ` Alex Williamson
2010-07-29 14:27 ` Michael S. Tsirkin
2010-07-30 20:42 ` Alex Williamson
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=20100720202030.GC11991@suse.de \
--to=gregkh@suse.de \
--cc=aafabbri@cisco.com \
--cc=alex.williamson@redhat.com \
--cc=arnd@arndb.de \
--cc=avi@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=hjk@linutronix.de \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mst@redhat.com \
--cc=p.jaroszynski@gmail.com \
--cc=pugs@cisco.com \
--cc=randy.dunlap@oracle.com \
--cc=scofeldm@cisco.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.