From: Zhenzhong Duan <zhenzhong.duan@intel.com>
To: qemu-devel@nongnu.org
Cc: alex.williamson@redhat.com, clg@redhat.com,
eric.auger@redhat.com, levon@movementarian.org,
Zhenzhong Duan <zhenzhong.duan@intel.com>
Subject: [PATCH v2 0/3] Optimize unmap_all with one ioctl()
Date: Thu, 9 Oct 2025 00:01:31 -0400 [thread overview]
Message-ID: <20251009040134.334251-1-zhenzhong.duan@intel.com> (raw)
Currently unmap_all is split into two ioctl() with each unmap half of
the whole iova space.
IOMMUFD supports unmap_all ioctl() from beginning, after kernel commit
c19650995374 ("vfio/type1: implement unmap all") added same support
for VFIO type1, the split becomes unnecessary.
So optimize the code to only do one ioctl() to unmap_all for both
backends.
Test:
In order to trigger unmap_all request, I have to fake a unmap_all request
on x86. Maybe it's easy to trigger unmap_all with other arch, e.g., arm smmu,
but for x86, iommu memory region is split by iommu_ir, unmap_all isn't
triggered by default. See
https://github.com/yiliu1765/qemu/commit/7afc7adac8fa601abd978b821c86e90e073d31ba
for details.
Thanks
Zhenzhong
Changelog:
v2:
- check unmap_all_supported instead of ioctl() for every unmap_all (John Levon)
- make assertion a separate patch (Cedric)
- pass VFIOLegacyContainer pointer in vfio_legacy_dma_unmap_one() (Cedric)
Zhenzhong Duan (3):
vfio/container: Support unmap all in one ioctl()
vfio/iommufd: Support unmap all in one ioctl()
vfio/listener: Add an assertion for unmap_all
include/hw/vfio/vfio-container-legacy.h | 1 +
hw/vfio/container-legacy.c | 38 ++++++++++++++-----------
hw/vfio/iommufd.c | 15 +---------
hw/vfio/listener.c | 1 +
4 files changed, 25 insertions(+), 30 deletions(-)
--
2.47.1
next reply other threads:[~2025-10-09 4:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-09 4:01 Zhenzhong Duan [this message]
2025-10-09 4:01 ` [PATCH v2 1/3] vfio/container: Support unmap all in one ioctl() Zhenzhong Duan
2025-10-09 4:01 ` [PATCH v2 2/3] vfio/iommufd: " Zhenzhong Duan
2025-10-09 4:01 ` [PATCH v2 3/3] vfio/listener: Add an assertion for unmap_all Zhenzhong Duan
2025-10-09 7:35 ` [PATCH v2 0/3] Optimize unmap_all with one ioctl() Cédric Le Goater
2025-10-09 8:05 ` Cédric Le Goater
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=20251009040134.334251-1-zhenzhong.duan@intel.com \
--to=zhenzhong.duan@intel.com \
--cc=alex.williamson@redhat.com \
--cc=clg@redhat.com \
--cc=eric.auger@redhat.com \
--cc=levon@movementarian.org \
--cc=qemu-devel@nongnu.org \
/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).