From: Matthew Rosato <mjrosato@linux.ibm.com>
To: thuth@redhat.com, qemu-s390x@nongnu.org, qemu-devel@nongnu.org
Cc: farman@linux.ibm.com, pmorel@linux.ibm.com, david@redhat.com,
cohuck@redhat.com, richard.henderson@linaro.org,
pasic@linux.ibm.com, borntraeger@linux.ibm.com
Subject: [PATCH v2 0/4] s390x/pci: some small fixes
Date: Fri, 3 Dec 2021 07:32:17 -0500 [thread overview]
Message-ID: <20211203123221.420101-1-mjrosato@linux.ibm.com> (raw)
A collection of small fixes for s390x PCI (not urgent). The first 3 are
fixes related to always using the host-provided CLP value when provided
vs a hard-coded value. The last patch adds logic for QEMU to report a
proper DTSM clp response rather than just 0s (guest linux doesn't look
at this field today).
Changes for v2:
- Add review tags (thanks!)
- Fix patch 4 (copy into guest payload)
- Small change to commit message for patches 1 & 4 (Pierre)
Matthew Rosato (4):
s390x/pci: use a reserved ID for the default PCI group
s390x/pci: don't use hard-coded dma range in reg_ioat
s390x/pci: use the passthrough measurement update interval
s390x/pci: add supported DT information to clp response
hw/s390x/s390-pci-bus.c | 1 +
hw/s390x/s390-pci-inst.c | 15 +++++++++------
hw/s390x/s390-pci-vfio.c | 1 +
include/hw/s390x/s390-pci-bus.h | 3 ++-
include/hw/s390x/s390-pci-clp.h | 3 ++-
5 files changed, 15 insertions(+), 8 deletions(-)
--
2.27.0
next reply other threads:[~2021-12-03 12:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 12:32 Matthew Rosato [this message]
2021-12-03 12:32 ` [PATCH v2 1/4] s390x/pci: use a reserved ID for the default PCI group Matthew Rosato
2021-12-03 12:32 ` [PATCH v2 2/4] s390x/pci: don't use hard-coded dma range in reg_ioat Matthew Rosato
2021-12-03 12:32 ` [PATCH v2 3/4] s390x/pci: use the passthrough measurement update interval Matthew Rosato
2021-12-03 12:32 ` [PATCH v2 4/4] s390x/pci: add supported DT information to clp response Matthew Rosato
2021-12-03 12:48 ` Pierre Morel
2021-12-03 12:48 ` 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=20211203123221.420101-1-mjrosato@linux.ibm.com \
--to=mjrosato@linux.ibm.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=farman@linux.ibm.com \
--cc=pasic@linux.ibm.com \
--cc=pmorel@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.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).