From: Pierre Morel <pmorel@linux.ibm.com>
To: walling@linux.ibm.com
Cc: borntraeger@de.ibm.com, cohuck@redhat.com, rth@twiddle.net,
david@redhat.com, qemu-s390x@nongnu.org, qemu-devel@nongnu.org,
pasic@linux.ibm.com, thuth@redhat.com
Subject: [Qemu-devel] [PATCH v1 0/3] [RFC] get real IOMMU information from VFIO IOMMU
Date: Wed, 9 Jan 2019 13:41:17 +0100 [thread overview]
Message-ID: <1547037680-21458-1-git-send-email-pmorel@linux.ibm.com> (raw)
In the Z-Architecture, the IOMMU information may change on a device
basis.
until this patch series we used hardcoded values to define the
IOMMU aperture we provide to the guest during PCI enumeration.
Let's ask the host about the IOMMU specific configuration using
VFIO capabilities.
NOTES:
1- You will need the according Linux patch to test this.
2- I am really not happy to add S390 dedicated code in the
VFIO common code, as do SPAPR, but I did not find a better
solution.
Any idea?
Pierre Morel (3):
vfio: Linux header placeholder
vfio/pci: Get real IOMMU information from container
s390x/pci: Reporting the host aperture to the guest
hw/s390x/s390-pci-bus.c | 2 +-
hw/s390x/s390-pci-bus.h | 3 ++
hw/s390x/s390-pci-inst.c | 20 ++++++++++--
hw/vfio/common.c | 75 +++++++++++++++++++++++++++++++++----------
include/hw/vfio/vfio-common.h | 3 ++
linux-headers/linux/vfio.h | 65 +++++++++++++++++++++++++++++++++++--
6 files changed, 144 insertions(+), 24 deletions(-)
--
2.7.4
next reply other threads:[~2019-01-09 12:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-09 12:41 Pierre Morel [this message]
2019-01-09 12:41 ` [Qemu-devel] [PATCH v1 1/3] vfio: Linux header placeholder Pierre Morel
2019-01-09 12:41 ` [Qemu-devel] [PATCH v1 2/3] vfio/pci: Get real IOMMU information from container Pierre Morel
2019-01-09 12:41 ` [Qemu-devel] [PATCH v1 3/3] s390x/pci: Reporting the host aperture to the guest Pierre Morel
2019-01-13 14:29 ` [Qemu-devel] [PATCH v1 0/3] [RFC] get real IOMMU information from VFIO IOMMU no-reply
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=1547037680-21458-1-git-send-email-pmorel@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--cc=thuth@redhat.com \
--cc=walling@linux.ibm.com \
/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).