From: Matthew Rosato <mjrosato@linux.ibm.com>
To: alex.williamson@redhat.com, cohuck@redhat.com, schnelle@linux.ibm.com
Cc: pmorel@linux.ibm.com, borntraeger@de.ibm.com, hca@linux.ibm.com,
gor@linux.ibm.com, gerald.schaefer@linux.ibm.com,
linux-s390@vger.kernel.org, kvm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/4] Pass zPCI hardware information via VFIO
Date: Sat, 19 Sep 2020 11:28:34 -0400 [thread overview]
Message-ID: <1600529318-8996-1-git-send-email-mjrosato@linux.ibm.com> (raw)
This patchset provides a means by which hardware information about the
underlying PCI device can be passed up to userspace (ie, QEMU) so that
this hardware information can be used rather than previously hard-coded
assumptions. A new VFIO region type is defined which holds this
information.
A form of these patches saw some rounds last year but has been back-
tabled for a while. The original work for this feature was done by Pierre
Morel. I'd like to refresh the discussion on this and get this finished up
so that we can move forward with better-supporting additional types of
PCI-attached devices. The proposal here presents a completely different
region mapping vs the prior approach, taking inspiration from vfio info
capability chains to provide device CLP information in a way that allows
for future expansion (new CLP features).
This feature is toggled via the CONFIG_VFIO_PCI_ZDEV configuration entry.
Matthew Rosato (4):
s390/pci: stash version in the zpci_dev
s390/pci: track whether util_str is valid in the zpci_dev
vfio-pci/zdev: define the vfio_zdev header
vfio-pci/zdev: use a device region to retrieve zPCI information
arch/s390/include/asm/pci.h | 4 +-
arch/s390/pci/pci_clp.c | 2 +
drivers/vfio/pci/Kconfig | 13 ++
drivers/vfio/pci/Makefile | 1 +
drivers/vfio/pci/vfio_pci.c | 8 ++
drivers/vfio/pci/vfio_pci_private.h | 10 ++
drivers/vfio/pci/vfio_pci_zdev.c | 242 ++++++++++++++++++++++++++++++++++++
include/uapi/linux/vfio.h | 5 +
include/uapi/linux/vfio_zdev.h | 116 +++++++++++++++++
9 files changed, 400 insertions(+), 1 deletion(-)
create mode 100644 drivers/vfio/pci/vfio_pci_zdev.c
create mode 100644 include/uapi/linux/vfio_zdev.h
--
1.8.3.1
next reply other threads:[~2020-09-19 15:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-19 15:28 Matthew Rosato [this message]
2020-09-19 15:28 ` [PATCH 1/4] s390/pci: stash version in the zpci_dev Matthew Rosato
2020-09-21 9:35 ` Niklas Schnelle
2020-09-21 9:38 ` Christian Borntraeger
2020-09-21 15:01 ` Cornelia Huck
2020-09-21 15:44 ` Matthew Rosato
2020-09-21 15:49 ` Cornelia Huck
2020-09-19 15:28 ` [PATCH 2/4] s390/pci: track whether util_str is valid " Matthew Rosato
2020-09-21 9:38 ` Christian Borntraeger
2020-09-21 9:41 ` Niklas Schnelle
2020-09-22 14:06 ` Matthew Rosato
2020-09-19 15:28 ` [PATCH 3/4] vfio-pci/zdev: define the vfio_zdev header Matthew Rosato
2020-09-22 10:54 ` Cornelia Huck
2020-09-22 13:55 ` Matthew Rosato
2020-09-19 15:28 ` [PATCH 4/4] vfio-pci/zdev: use a device region to retrieve zPCI information Matthew Rosato
2020-09-22 11:22 ` Cornelia Huck
2020-09-22 14:02 ` Matthew Rosato
2020-09-19 15:50 ` [PATCH 0/4] Pass zPCI hardware information via VFIO 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=1600529318-8996-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=gerald.schaefer@linux.ibm.com \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=pmorel@linux.ibm.com \
--cc=schnelle@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