qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: qemu-devel@nongnu.org
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
	Alex Williamson <alex.williamson@redhat.com>,
	qemu-ppc@nongnu.org, Alexander Graf <agraf@suse.de>,
	Gavin Shan <gwshan@linux.vnet.ibm.com>
Subject: [Qemu-devel] [PATCH v9 0/4] vfio on spapr-ppc64
Date: Tue, 10 Jun 2014 15:39:20 +1000	[thread overview]
Message-ID: <1402378764-1870-1-git-send-email-aik@ozlabs.ru> (raw)

Yet another try with VFIO on SPAPR (server PPC64).

This adds VFIO support on SPAPR for the existing VFIO-SPAPR-TCE driver
in the upstream kernel.

Individual patches have more detailed commit logs.

Please comment. Thanks!


Changes:
v9:
* fixed comments about VFIO_IOMMU_DISABLE
* added checking stub for container fd ioctls

v8:
* added placeholder for KVM_CAP_SPAPR_TCE_VFIO capability
* added generic helper to call ioctl on container's fd.

v7:
* cleaned and rebased on agraf/ppc-next tree (which is on its way to upstream)

v6:
* initial set was split into 3

v5:
* rebase on top of the current upstream

v4:
* addressed all comments from Alex Williamson
* moved spapr-pci-phb-vfio-phb to new file
* split spapr-pci-phb-vfio to many smaller patches

Alexey Kardashevskiy (4):
  spapr_iommu: Make in-kernel TCE table optional
  vfio: Add vfio_container_ioctl()
  spapr_pci_vfio: Add spapr-pci-vfio-host-bridge to support vfio
  vfio: Enable for SPAPR

 hw/misc/vfio.c              |  78 +++++++++++++++++++++++++++++++++
 hw/ppc/Makefile.objs        |   3 ++
 hw/ppc/spapr_iommu.c        |   7 ++-
 hw/ppc/spapr_pci.c          |   2 +-
 hw/ppc/spapr_pci_vfio.c     | 102 ++++++++++++++++++++++++++++++++++++++++++++
 hw/ppc/spapr_vio.c          |   2 +-
 include/hw/misc/vfio.h      |   9 ++++
 include/hw/pci-host/spapr.h |  11 +++++
 include/hw/ppc/spapr.h      |   4 +-
 target-ppc/kvm.c            |   7 ++-
 target-ppc/kvm_ppc.h        |   6 ++-
 11 files changed, 222 insertions(+), 9 deletions(-)
 create mode 100644 hw/ppc/spapr_pci_vfio.c
 create mode 100644 include/hw/misc/vfio.h

-- 
2.0.0

             reply	other threads:[~2014-06-10  5:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-10  5:39 Alexey Kardashevskiy [this message]
2014-06-10  5:39 ` [Qemu-devel] [PATCH v9 1/4] spapr_iommu: Make in-kernel TCE table optional Alexey Kardashevskiy
2014-06-10  5:39 ` [Qemu-devel] [PATCH v9 2/4] vfio: Add vfio_container_ioctl() Alexey Kardashevskiy
2014-06-11 20:16   ` Alex Williamson
2014-06-11 20:17   ` Alex Williamson
2014-06-10  5:39 ` [Qemu-devel] [PATCH v9 3/4] spapr_pci_vfio: Add spapr-pci-vfio-host-bridge to support vfio Alexey Kardashevskiy
2014-06-19 13:57   ` Alexey Kardashevskiy
2014-06-10  5:39 ` [Qemu-devel] [PATCH v9 4/4] vfio: Enable for SPAPR Alexey Kardashevskiy
2014-06-11 20:16   ` Alex Williamson
2014-06-23 17:01 ` [Qemu-devel] [PATCH v9 0/4] vfio on spapr-ppc64 Alexander Graf

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=1402378764-1870-1-git-send-email-aik@ozlabs.ru \
    --to=aik@ozlabs.ru \
    --cc=agraf@suse.de \
    --cc=alex.williamson@redhat.com \
    --cc=gwshan@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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;
as well as URLs for NNTP newsgroup(s).