From: Matthew Rosato <mjrosato@linux.ibm.com>
To: cohuck@redhat.com
Cc: walling@linux.ibm.com, alex.williamson@redhat.com,
pmorel@linux.ibm.com, david@redhat.com, mst@redhat.com,
qemu-devel@nongnu.org, pasic@linux.ibm.com,
borntraeger@de.ibm.com, qemu-s390x@nongnu.org,
pbonzini@redhat.com, rth@twiddle.net
Subject: [Qemu-devel] [PATCH v3 0/5] Retrieving zPCI specific info from QEMU
Date: Fri, 6 Sep 2019 20:16:24 -0400 [thread overview]
Message-ID: <1567815389-18229-1-git-send-email-mjrosato@linux.ibm.com> (raw)
Note: These patches by Pierre got lost in the ether a few months back
as he has been unavailable to carry them forward. I've made changes
based upon comments received on the kernel part of his last version.
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 v4 0/4] Retrieving zPCI specific info with VFIO
We use the PCI VFIO interface to retrieve ZPCI specific information
from the host with a ZPCI specific device region.
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.
Changes since v2:
- update vfio_zdev.h to match kernel + fix packing attribute
- update vfio.h to match kernel changes
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 | 145 +++++++++++++++++++++++++--
hw/s390x/s390-pci-bus.h | 15 ++-
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 | 7 +-
linux-headers/linux/vfio_zdev.h | 35 +++++++
7 files changed, 417 insertions(+), 220 deletions(-)
create mode 100644 hw/s390x/s390-pci-clp.h
create mode 100644 linux-headers/linux/vfio_zdev.h
--
1.8.3.1
next reply other threads:[~2019-09-07 0:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-07 0:16 Matthew Rosato [this message]
2019-09-07 0:16 ` [Qemu-devel] [PATCH v3 1/5] vfio: vfio_iommu_type1: linux header place holder Matthew Rosato
2019-09-08 13:08 ` Michael S. Tsirkin
2019-09-07 0:16 ` [Qemu-devel] [PATCH v3 2/5] s390: PCI: Creation a header dedicated to PCI CLP Matthew Rosato
2019-09-07 0:16 ` [Qemu-devel] [PATCH v3 3/5] s390: vfio_pci: Use a PCI Group structure Matthew Rosato
2019-09-09 5:18 ` [Qemu-devel] [qemu-s390x] " Thomas Huth
2019-09-09 16:21 ` Matthew Rosato
2019-09-07 0:16 ` [Qemu-devel] [PATCH v3 4/5] s390: vfio_pci: Use a PCI Function structure Matthew Rosato
2019-09-07 0:16 ` [Qemu-devel] [PATCH v3 5/5] s390: vfio_pci: Get zPCI function info from host Matthew Rosato
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=1567815389-18229-1-git-send-email-mjrosato@linux.ibm.com \
--to=mjrosato@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.ibm.com \
--cc=pbonzini@redhat.com \
--cc=pmorel@linux.ibm.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).