From: Aaron Lewis <aaronlewis@google.com>
To: kvm@vger.kernel.org
Cc: alex@shazbot.org, dmatlack@google.com, jgg@nvidia.com,
Aaron Lewis <aaronlewis@google.com>
Subject: [PATCH v2 0/4] Introduce vfio_dma_mapping_perf_test
Date: Tue, 4 Aug 2026 16:57:44 +0000 [thread overview]
Message-ID: <20260804165748.1060476-1-aaronlewis@google.com> (raw)
Add a new VFIO selftest, vfio_dma_mapping_perf_test, to provide a
configurable tool for measuring DMA mapping and unmapping latencies.
This selftest introduces command-line parameters to provide a convenient
way to tune the test for specific situations. For example, it can be used
to observe the lengthy unmap times of the Type 1 IOMMU on large memory
regions, or to compare DMA mapping performance between the Type 1 IOMMU
and IOMMUFD. These scenarios can now be easily configured and run via the
command line.
Changes in V2:
- Assert expected unmap size in iommu_unmap().
- Remove unused struct iommu_mapping
- Create a reusable TIME() macro and move timer-related helpers to libvfio to
output nanoseconds
- Unified latency reporting by pulling over the TIME() macro instead of
distinct test-specific prints.
- Drop confusing prints mixing size/addresses in favor of parsing-friendly
outputs.
- Fix potentially undefined behavior on 32-bit caused by passing u64 directly
to %lu.
- Refactored memfd tests to run only on MODE_IOMMUFD and drop redundant
variants.
- Removed MAP_SHARED from memfd_create flags to avoid inadvertently aliasing
MFD_CLOEXEC.
- Fixed memfd_create() return validation to correctly verify against < 0.
- Updated the map/unmap failure block to properly abort/SKIP on ENOMEM hugepage
failures.
- Store the device_bdf parameter statically within test_params to unify
configuration definitions.
- Eliminate memory leaks in populate_harness_args by correctly piping argv into
wordexp with WRDE_APPEND on subsequent uses. Subsequent uses now works whether
- Halt execution and exit gracefully if invalid configurations or the
"-h" flag are supplied, preventing test execution dropout.
Aaron Lewis (4):
vfio: selftests: Assert the region was unmapped in iommu_unmap()
vfio: selftests: Introduce vfio_dma_mapping_perf_test
vfio: selftests: Add memfd test to vfio_dma_mapping_perf_test
vfio: selftests: Allow a size for vfio_dma_mapping_perf_test
tools/testing/selftests/vfio/Makefile | 1 +
.../selftests/vfio/lib/include/libvfio.h | 28 ++
.../vfio/lib/include/libvfio/iommu.h | 12 +-
tools/testing/selftests/vfio/lib/iommu.c | 24 ++
.../vfio/vfio_dma_mapping_perf_test.c | 331 ++++++++++++++++++
.../selftests/vfio/vfio_dma_mapping_test.c | 11 +-
6 files changed, 397 insertions(+), 10 deletions(-)
create mode 100644 tools/testing/selftests/vfio/vfio_dma_mapping_perf_test.c
--
2.55.0.654.g21b8a5bc05-goog
next reply other threads:[~2026-08-04 16:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-04 16:57 Aaron Lewis [this message]
2026-08-04 16:57 ` [PATCH v2 1/4] vfio: selftests: Assert the region was unmapped in iommu_unmap() Aaron Lewis
2026-08-04 16:57 ` [PATCH v2 2/4] vfio: selftests: Introduce vfio_dma_mapping_perf_test Aaron Lewis
2026-08-04 17:15 ` sashiko-bot
2026-08-04 16:57 ` [PATCH v2 3/4] vfio: selftests: Add memfd test to vfio_dma_mapping_perf_test Aaron Lewis
2026-08-04 16:57 ` [PATCH v2 4/4] vfio: selftests: Allow a size for vfio_dma_mapping_perf_test Aaron Lewis
2026-08-04 17:11 ` sashiko-bot
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=20260804165748.1060476-1-aaronlewis@google.com \
--to=aaronlewis@google.com \
--cc=alex@shazbot.org \
--cc=dmatlack@google.com \
--cc=jgg@nvidia.com \
--cc=kvm@vger.kernel.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