Kernel KVM virtualization development
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: kvm@vger.kernel.org, qemu-devel@nongnu.org
Cc: pugs@cisco.com, chrisw@redhat.com, mst@redhat.com,
	alex.williamson@redhat.com
Subject: [RFC PATCH 0/5] QEMU VFIO device assignment
Date: Sun, 11 Jul 2010 12:09:10 -0600	[thread overview]
Message-ID: <20100711180910.20121.93313.stgit@localhost6.localdomain6> (raw)

The following series implements QEMU device assignment using the
proposed VFIO/UIOMMU kernel interfaces.  See the last patch for
further vfio description.  I've tested this on the v2 VFIO patch,
with a number of fixes hacked in along the way.  I'll update when
Tom releases a new version of VFIO.  Hopefully this will provide
some support for the usefulness of such an interfaces.  Thanks,

Alex

---

Alex Williamson (5):
      VFIO based device assignment
      APIC/IOAPIC EOI callback
      RAM API: Make use of it for x86 PC
      Minimal RAM API support
      qemu_ram_map/unmap: Allow pre-allocated space to be mapped


 Makefile.target |    2 
 cpu-common.h    |    5 
 exec.c          |   56 ++
 hw/apic.c       |   18 +
 hw/apic.h       |    4 
 hw/ioapic.c     |   29 +
 hw/linux-vfio.h |  200 ++++++++
 hw/pc.c         |   12 -
 hw/pc.h         |   12 -
 hw/vfio.c       | 1295 +++++++++++++++++++++++++++++++++++++++++++++++++++++++
 hw/vfio.h       |   90 ++++
 memory.c        |   77 +++
 memory.h        |   23 +
 13 files changed, 1812 insertions(+), 11 deletions(-)
 create mode 100644 hw/linux-vfio.h
 create mode 100644 hw/vfio.c
 create mode 100644 hw/vfio.h
 create mode 100644 memory.c
 create mode 100644 memory.h


             reply	other threads:[~2010-07-11 18:09 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-11 18:09 Alex Williamson [this message]
2010-07-11 18:09 ` [RFC PATCH 1/5] qemu_ram_map/unmap: Allow pre-allocated space to be mapped Alex Williamson
2010-07-11 18:09 ` [RFC PATCH 2/5] Minimal RAM API support Alex Williamson
2010-07-11 18:18   ` Alex Williamson
2010-07-11 18:20   ` Avi Kivity
2010-07-11 18:24     ` Alex Williamson
2010-07-11 18:29       ` Avi Kivity
2010-07-11 18:09 ` [RFC PATCH 3/5] RAM API: Make use of it for x86 PC Alex Williamson
2010-07-11 18:09 ` [RFC PATCH 4/5] APIC/IOAPIC EOI callback Alex Williamson
2010-07-11 18:14   ` Avi Kivity
2010-07-11 18:26     ` Alex Williamson
2010-07-11 18:30       ` Avi Kivity
2010-07-11 18:54         ` Michael S. Tsirkin
2010-07-11 19:21           ` Alex Williamson
2010-07-11 19:23             ` Michael S. Tsirkin
2010-07-11 20:03               ` Alex Williamson
2010-07-11 20:05                 ` Michael S. Tsirkin
2010-07-11 20:12                 ` Michael S. Tsirkin
2010-07-11 21:59                   ` Alex Williamson
2010-07-12  6:33         ` Avi Kivity
2010-07-12  9:05           ` Gleb Natapov
2010-07-12  9:13             ` Avi Kivity
2010-07-11 18:09 ` [RFC PATCH 5/5] VFIO based device assignment Alex Williamson
2010-07-11 18:27   ` Avi Kivity
2010-07-11 19:38     ` Alex Williamson
2010-07-12  6:37       ` Avi Kivity
2010-07-11 18:17 ` [RFC PATCH 0/5] QEMU VFIO " Avi Kivity
2010-07-11 18:37   ` Alex Williamson
2010-07-11 18:43     ` Avi Kivity
2010-07-11 20:24       ` Alex Williamson
2010-07-12  6:29         ` Avi Kivity
2010-07-12 11:03           ` 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=20100711180910.20121.93313.stgit@localhost6.localdomain6 \
    --to=alex.williamson@redhat.com \
    --cc=chrisw@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=mst@redhat.com \
    --cc=pugs@cisco.com \
    --cc=qemu-devel@nongnu.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