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, Gavin Shan <gwshan@linux.vnet.ibm.com>,
David Gibson <david@gibson.dropbear.id.au>
Subject: [Qemu-devel] [PATCH qemu v2 0/2] spapr_pci: Merge spapr-vfio-phb into spapr-phb
Date: Thu, 3 Sep 2015 14:40:29 +1000 [thread overview]
Message-ID: <1441255231-18569-1-git-send-email-aik@ozlabs.ru> (raw)
This allows sharing the same PHB for both emulated and VFIO devices.
This used to be a part of the Dynamic DMA window patchset. Since it was
moved out and reworked quite a lot, all reviewed-by's got outdated.
This is based on dgibson/spapr-next sha1 f91ffef.
Please comment. Thanks.
Changes:
v2:
* fixed bus_offset
* moved DMA setup to a spapr_phb_dma_reset() helper - DDW patches would
add it anyway
* verified that migration still works
Alexey Kardashevskiy (2):
spapr_pci_vfio: Remove redundant spapr-pci-vfio-host-bridge
spapr_pci: Remove constraints about VFIO-PCI devices
hw/ppc/Makefile.objs | 5 +-
hw/ppc/spapr_pci.c | 195 +++++++++++++++++++++++++++-----------------
hw/ppc/spapr_pci_vfio.c | 147 +++++++++++++--------------------
hw/vfio/common.c | 22 ++---
include/hw/pci-host/spapr.h | 23 +++---
include/hw/vfio/vfio.h | 3 +-
6 files changed, 195 insertions(+), 200 deletions(-)
--
2.4.0.rc3.8.gfb3e7d5
next reply other threads:[~2015-09-03 4:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-03 4:40 Alexey Kardashevskiy [this message]
2015-09-03 4:40 ` [Qemu-devel] [PATCH qemu v2 1/2] spapr_pci_vfio: Remove redundant spapr-pci-vfio-host-bridge Alexey Kardashevskiy
2015-09-03 4:40 ` [Qemu-devel] [PATCH qemu v2 2/2] spapr_pci: Remove constraints about VFIO-PCI devices Alexey Kardashevskiy
2015-09-10 2:43 ` Alex Williamson
2015-09-11 20:03 ` Alex Williamson
2015-09-14 4:04 ` David Gibson
2015-09-14 8:56 ` Alexey Kardashevskiy
2015-09-14 11:42 ` David Gibson
2015-09-14 14:37 ` 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=1441255231-18569-1-git-send-email-aik@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=alex.williamson@redhat.com \
--cc=david@gibson.dropbear.id.au \
--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).