From: Pierre Morel <pmorel@linux.ibm.com>
To: cohuck@redhat.com
Cc: pasic@linux.vnet.ibm.com, mst@redhat.com, qemu-s390x@nongnu.org,
david@redhat.com, walling@linux.ibm.com, qemu-devel@nongnu.org,
borntraeger@de.ibm.com, alex.williamson@redhat.com,
pbonzini@redhat.com, rth@twiddle.net
Subject: [Qemu-devel] [PATCH 0/5] Retrieving zPCI specific info from QEMU
Date: Fri, 10 May 2019 16:38:48 +0200 [thread overview]
Message-ID: <1557499133-24169-1-git-send-email-pmorel@linux.ibm.com> (raw)
This patch implement the QEMU part to retrieve ZPCI specific
information from the host.
The Linux part has been posted on a separate patch on the LKML.
Subject: [PATCH 0/4] Retrieving zPCI specific info with VFIO
Message-Id: <1557476555-20256-1-git-send-email-pmorel@linux.ibm.com>
We use the PCI VFIO interface to retrieve ZPCI specific information
from the host.
The Linux patch enhance the VFIO_IOMMU_GET_INFO ioctl with
a new Z specific capability and we use it to access the
information stored in the zPCI function.
The retrieval is done only once per function and function group
during the plugging of the device.
The guest's requests are filled with shadow values we keep for
the duration of the device remains plugged.
Still there are some values we need to virtualize, like
the UID and FID of the zPCI function, and we currently
only allow the refresh bit for the zPCI group flags.
Note that we export the CLP specific definitions in a dedicated
file for clarity.
Pierre Morel (5):
vfio: vfio_iommu_type1: linux header place holder
s390: PCI: Creation a header dedicated to PCI CLP
s390: vfio_pci: Use a PCI Group structure
s390: vfio_pci: Use a PCI Function structure
s390: vfio_pci: Get zPCI function info from host
hw/s390x/s390-pci-bus.c | 142 ++++++++++++++++++++++++++++--
hw/s390x/s390-pci-bus.h | 13 ++-
hw/s390x/s390-pci-clp.h | 211 +++++++++++++++++++++++++++++++++++++++++++++
hw/s390x/s390-pci-inst.c | 28 +++---
hw/s390x/s390-pci-inst.h | 196 -----------------------------------------
linux-headers/linux/vfio.h | 16 +++-
6 files changed, 386 insertions(+), 220 deletions(-)
create mode 100644 hw/s390x/s390-pci-clp.h
--
2.7.4
next reply other threads:[~2019-05-10 14:40 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-10 14:38 Pierre Morel [this message]
2019-05-10 14:38 ` [Qemu-devel] [PATCH 1/5] vfio: vfio_iommu_type1: linux header place holder Pierre Morel
2019-05-12 18:22 ` Michael S. Tsirkin
2019-05-16 8:51 ` Pierre Morel
2019-05-10 14:38 ` [Qemu-devel] [PATCH 2/5] s390: PCI: Creation a header dedicated to PCI CLP Pierre Morel
2019-05-10 14:38 ` [Qemu-devel] [PATCH 3/5] s390: vfio_pci: Use a PCI Group structure Pierre Morel
2019-05-14 11:49 ` Cornelia Huck
2019-05-16 8:55 ` Pierre Morel
2019-05-10 14:38 ` [Qemu-devel] [PATCH 4/5] s390: vfio_pci: Use a PCI Function structure Pierre Morel
2019-05-10 14:38 ` [Qemu-devel] [PATCH 5/5] s390: vfio_pci: Get zPCI function info from host Pierre Morel
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=1557499133-24169-1-git-send-email-pmorel@linux.ibm.com \
--to=pmorel@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=mst@redhat.com \
--cc=pasic@linux.vnet.ibm.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=rth@twiddle.net \
--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).