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 v7 0/4] vfio on spapr-ppc64
Date: Thu, 5 Jun 2014 15:49:57 +1000 [thread overview]
Message-ID: <1401947401-21329-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.
While patch #1 is questionable, others are pretty much ready to but
I do not know via which maintainer tree - Alex or Alex? :)
Please comment. Thanks!
Changes:
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_spapr_get_info()
spapr_pci_vfio: Add spapr-pci-vfio-host-bridge to support vfio
vfio: Enable for spapr
hw/misc/vfio.c | 64 +++++++++++++++++++++++++++++++
hw/ppc/Makefile.objs | 3 ++
hw/ppc/spapr_iommu.c | 6 ++-
hw/ppc/spapr_pci.c | 2 +-
hw/ppc/spapr_pci_vfio.c | 93 +++++++++++++++++++++++++++++++++++++++++++++
hw/ppc/spapr_vio.c | 2 +-
include/hw/misc/vfio.h | 11 ++++++
include/hw/pci-host/spapr.h | 11 ++++++
include/hw/ppc/spapr.h | 4 +-
9 files changed, 191 insertions(+), 5 deletions(-)
create mode 100644 hw/ppc/spapr_pci_vfio.c
create mode 100644 include/hw/misc/vfio.h
--
2.0.0
next reply other threads:[~2014-06-05 5:50 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-05 5:49 Alexey Kardashevskiy [this message]
2014-06-05 5:49 ` [Qemu-devel] [PATCH v7 1/4] spapr_iommu: Make in-kernel TCE table optional Alexey Kardashevskiy
2014-06-05 6:43 ` Alexey Kardashevskiy
2014-06-05 13:06 ` Alexander Graf
2014-06-05 13:10 ` Alexey Kardashevskiy
2014-06-05 13:15 ` Alexander Graf
2014-06-05 13:33 ` Alexey Kardashevskiy
2014-06-05 13:36 ` Alexander Graf
2014-06-05 14:33 ` Alexey Kardashevskiy
2014-06-05 16:51 ` Alexander Graf
2014-06-05 23:17 ` Alexey Kardashevskiy
2014-06-05 23:36 ` Alexander Graf
2014-06-05 23:48 ` Alexey Kardashevskiy
2014-06-06 3:38 ` Benjamin Herrenschmidt
2014-06-05 5:49 ` [Qemu-devel] [PATCH v7 2/4] vfio: Add vfio_container_spapr_get_info() Alexey Kardashevskiy
2014-06-05 19:27 ` Alex Williamson
2014-06-05 23:40 ` Alexey Kardashevskiy
2014-06-06 1:32 ` Gavin Shan
2014-06-05 5:50 ` [Qemu-devel] [PATCH v7 3/4] spapr_pci_vfio: Add spapr-pci-vfio-host-bridge to support vfio Alexey Kardashevskiy
2014-06-05 13:34 ` Alexander Graf
2014-06-05 14:37 ` Alexey Kardashevskiy
2014-06-05 5:50 ` [Qemu-devel] [PATCH v7 4/4] vfio: Enable for spapr Alexey Kardashevskiy
2014-06-05 19:31 ` Alex Williamson
2014-06-05 23:39 ` Alexey Kardashevskiy
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=1401947401-21329-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).