From: Tom Lyon <pugs@cisco.com>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: linux-pci@vger.kernel.org, jbarnes@virtuousgeek.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
randy.dunlap@oracle.com, arnd@arndb.de, joro@8bytes.org,
hjk@linutronix.de, avi@redhat.com, gregkh@suse.de,
chrisw@sous-sol.org, mst@redhat.com
Subject: Re: [PATCH 3/3] VFIO V4: VFIO driver: Non-privileged user level PCI drivers
Date: Fri, 15 Oct 2010 15:29:13 -0700 [thread overview]
Message-ID: <201010151529.13571.pugs@cisco.com> (raw)
In-Reply-To: <1285620073.4951.44.camel@x201>
Michael & Alex et al -
Sorry for going quiet; I've been digesting the comments and researching a
lot more stuff. I plan to release V5 shortly after 2.6.36 is out, highlights
will be:
1. Re-written pci config tables - using approach suggested by MST to clean
things up. Looking much better. Also fixed endian issues.
2. Clean up ROM bar handling. Now only read() system call can access rom bar;
it is always disabled afterwards.
3. Clean up pci_iomap and pci_request_regions handling. Allocates on demand
but frees all on close.
4. Resets device on open. Disables, but does not do full reset on close due to
lock problem with remove() callers.
5. Fixed up memlock rlimit accounting.
6. Lots of small cleanups.
Stay tuned.
I'm also looking at adding PCIe extended capabilities - got a request from a
cisco project.
next prev parent reply other threads:[~2010-10-15 22:29 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-22 21:18 [PATCH 3/3] VFIO V4: VFIO driver: Non-privileged user level PCI drivers Tom Lyon
2010-09-26 14:54 ` Michael S. Tsirkin
2010-09-30 21:43 ` Tom Lyon
2010-10-03 12:27 ` Michael S. Tsirkin
2010-09-27 11:54 ` Michael S. Tsirkin
2010-09-27 20:57 ` Alex Williamson
2010-09-28 10:14 ` Michael S. Tsirkin
2010-09-30 23:09 ` Tom Lyon
2010-10-03 13:02 ` Michael S. Tsirkin
2010-09-27 20:41 ` Alex Williamson
2010-10-15 22:29 ` Tom Lyon [this message]
2010-09-27 20:46 ` Alex Williamson
2010-09-28 10:09 ` Michael S. Tsirkin
2010-09-28 14:26 ` Alex Williamson
2010-09-28 14:40 ` Michael S. Tsirkin
2010-09-28 17:10 ` Alex Williamson
2010-09-28 17:36 ` Michael S. Tsirkin
-- strict thread matches above, loose matches on Subject: below --
2010-09-23 12:58 Andy Walls
2010-09-23 19:33 ` Tom Lyon
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=201010151529.13571.pugs@cisco.com \
--to=pugs@cisco.com \
--cc=alex.williamson@redhat.com \
--cc=arnd@arndb.de \
--cc=avi@redhat.com \
--cc=chrisw@sous-sol.org \
--cc=gregkh@suse.de \
--cc=hjk@linutronix.de \
--cc=jbarnes@virtuousgeek.org \
--cc=joro@8bytes.org \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=mst@redhat.com \
--cc=randy.dunlap@oracle.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox