From: Alex Williamson <alex.williamson@redhat.com>
To: alex.williamson@redhat.com
Cc: aik@ozlabs.ru, benh@kernel.crashing.org,
linux-kernel@vger.kernel.org, kvm@vger.kernel.org,
david@gibson.dropbear.id.au
Subject: [PATCH 0/3] vfio-pci: VGA and legacy MMIO & I/O port access
Date: Mon, 14 Jan 2013 20:38:17 -0700 [thread overview]
Message-ID: <20130115033101.6894.50292.stgit@bling.home> (raw)
This series includes a couple cleanups that I'll target for 3.9 plus
RFC patch 3/3 that adds device regions for legacy I/O and makes use
of the VGA arbiter for enabling VGA assignment. I know the POWER
guys don't likely care about VGA support, but Alexey, Ben, and David,
I'd appreciate any feedback on the overal incorporation into vfio
given your history with the design. VGA is still a work in progress
but with this base I'm able to assign a handlful of desktop cards that
I have on hand to a qemu guest using standard builtin VGA drivers.
Thanks,
Alex
---
Alex Williamson (3):
vfio-pci: Cleanup read/write functions
vfio-pci: Cleanup BAR access
vfio-pci: Add support for legacy MMIO & I/O port towards VGA support
drivers/vfio/pci/Kconfig | 10 +
drivers/vfio/pci/vfio_pci.c | 106 +++++++++----
drivers/vfio/pci/vfio_pci_config.c | 5 -
drivers/vfio/pci/vfio_pci_private.h | 16 +-
drivers/vfio/pci/vfio_pci_rdwr.c | 282 +++++++++++++++++------------------
include/uapi/linux/vfio.h | 8 +
6 files changed, 242 insertions(+), 185 deletions(-)
next reply other threads:[~2013-01-15 3:38 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-15 3:38 Alex Williamson [this message]
2013-01-15 3:38 ` [PATCH 1/3] vfio-pci: Cleanup read/write functions Alex Williamson
2013-01-15 3:39 ` [PATCH 2/3] vfio-pci: Cleanup BAR access Alex Williamson
2013-01-15 3:39 ` [RFC PATCH 3/3] vfio-pci: Add support for legacy MMIO & I/O port towards VGA support 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=20130115033101.6894.50292.stgit@bling.home \
--to=alex.williamson@redhat.com \
--cc=aik@ozlabs.ru \
--cc=benh@kernel.crashing.org \
--cc=david@gibson.dropbear.id.au \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@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
all inboxes | Powered by JetHome®