From: Niklas Schnelle <schnelle@linux.ibm.com>
To: Alex Williamson <alex.williamson@redhat.com>,
Cornelia Huck <cohuck@redhat.com>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-s390@vger.kernel.org,
"Matthew Rosato" <mjrosato@linux.ibm.com>,
"Pierre Morel" <pmorel@linux.ibm.com>,
"Christian Bornträger" <borntraeger@linux.ibm.com>
Subject: [PATCH 0/1] vfio/type1: Fix vfio-pci pass-through of ISM devices
Date: Mon, 2 Jan 2023 10:34:51 +0100 [thread overview]
Message-ID: <20230102093452.761185-1-schnelle@linux.ibm.com> (raw)
Hi Alex,
Since commit cbf7827bc5dc ("iommu/s390: Fix potential s390_domain aperture
shrinking") the s390 IOMMU driver uses a reserved region instead of an
artificially shrunk aperture to restrict IOMMU use based on the system provided
DMA ranges of devices. While this is more aligned with the common code use
of apertures and reserved regions it turns out this currently breaks vfio-pci
pass-through of our special virtual ISM PCI device. Investigation showed that
this is due to vfio_test_domain_fgsp() ignoring the IOMMU reserved regions and
mapping IOVA address 0 even if that falls within a reserved region. Thus
I propose the below patch to make vfio_test_domain_fgsp() find a region to do
its mapping test instead of blindly using IOVA 0.
I did post the below patch independently already on December 22 but the subject
wording didn't make it clear that this fixes a real problem and of course the
holidays contribute to making things easier to miss so I wanted to post again
with a bit more background and a more catchy/clear subject on the cover letter.
As for testing, I tested this based on current master on both on s390 where it
skips the reserved 0x0-0x100000000 range and on an AMD Ryzen 3990X where it
continues to do the test on DMA address 0 and sets domain->fgsp to true.
Thanks,
Niklas Schnelle
Niklas Schnelle (1):
vfio/type1: Respect IOMMU reserved regions in vfio_test_domain_fgsp()
drivers/vfio/vfio_iommu_type1.c | 29 ++++++++++++++++++-----------
1 file changed, 18 insertions(+), 11 deletions(-)
--
2.34.1
next reply other threads:[~2023-01-02 9:35 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-02 9:34 Niklas Schnelle [this message]
2023-01-02 9:34 ` [PATCH 1/1] vfio/type1: Respect IOMMU reserved regions in vfio_test_domain_fgsp() Niklas Schnelle
2023-01-03 23:39 ` Jason Gunthorpe
2023-01-04 9:52 ` Niklas Schnelle
2023-01-04 12:16 ` Jason Gunthorpe
2023-01-04 13:08 ` Niklas Schnelle
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=20230102093452.761185-1-schnelle@linux.ibm.com \
--to=schnelle@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=borntraeger@linux.ibm.com \
--cc=cohuck@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@vger.kernel.org \
--cc=mjrosato@linux.ibm.com \
--cc=pmorel@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