From: Alex Mastro <amastro@fb.com>
To: Alex Williamson <alex@shazbot.org>,
David Matlack <dmatlack@google.com>,
Shuah Khan <shuah@kernel.org>
Cc: Peter Xu <peterx@redhat.com>, <linux-kernel@vger.kernel.org>,
<kvm@vger.kernel.org>, <linux-kselftest@vger.kernel.org>,
Jason Gunthorpe <jgg@ziepe.ca>, Alex Mastro <amastro@fb.com>
Subject: [PATCH v3 0/3] vfio: selftests: Add MMIO DMA mapping test
Date: Wed, 14 Jan 2026 10:57:15 -0800 [thread overview]
Message-ID: <20260114-map-mmio-test-v3-0-44e036d95e64@fb.com> (raw)
Test IOMMU mapping the BAR mmaps created during vfio_pci_device_setup().
All IOMMU modes are tested: vfio_type1 variants are expected to succeed,
while non-type1 modes are expected to fail. iommufd compat mode can be
updated to expect success once kernel support lands. Native iommufd will
not support mapping vaddrs backed by MMIO (it will support dma-buf based
MMIO mapping instead).
Changes in v3:
- Rename mmap_aligned() to mmap_reserve()
- Reorder variable declarations for reverse-fir-tree style
- Update patch 2 commit message to mention MADV_HUGEPAGE and MAP_FILE
- Move BAR size check into map_partial_bar test only
- Link to v2: https://lore.kernel.org/r/20260113-map-mmio-test-v2-0-e6d34f09c0bb@fb.com
Changes in v2:
- Split into patch series
- Factor out mmap_reserve() for vaddr alignment
- Align BAR mmaps to improve hugepage IOMMU mapping efficiency
- Centralize MODE_* string definitions
- Add is_power_of_2() assertion for BAR size
- Simplify align calculation to min(size, 1G)
- Add map_bar_misaligned test case
- Link to v1: https://lore.kernel.org/all/20260107-scratch-amastro-vfio-dma-mapping-mmio-test-v1-1-0cec5e9ec89b@fb.com
Signed-off-by: Alex Mastro <amastro@fb.com>
---
Alex Mastro (3):
vfio: selftests: Centralize IOMMU mode name definitions
vfio: selftests: Align BAR mmaps for efficient IOMMU mapping
vfio: selftests: Add vfio_dma_mapping_mmio_test
tools/testing/selftests/vfio/Makefile | 1 +
tools/testing/selftests/vfio/lib/include/libvfio.h | 9 ++
.../selftests/vfio/lib/include/libvfio/iommu.h | 6 +
tools/testing/selftests/vfio/lib/iommu.c | 12 +-
tools/testing/selftests/vfio/lib/libvfio.c | 25 ++++
tools/testing/selftests/vfio/lib/vfio_pci_device.c | 24 +++-
.../selftests/vfio/vfio_dma_mapping_mmio_test.c | 143 +++++++++++++++++++++
.../testing/selftests/vfio/vfio_dma_mapping_test.c | 2 +-
8 files changed, 214 insertions(+), 8 deletions(-)
---
base-commit: d721f52e31553a848e0e9947ca15a49c5674aef3
change-id: 20260112-map-mmio-test-b4e4c2d917a9
Best regards,
--
Alex Mastro <amastro@fb.com>
next reply other threads:[~2026-01-14 18:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 18:57 Alex Mastro [this message]
2026-01-14 18:57 ` [PATCH v3 1/3] vfio: selftests: Centralize IOMMU mode name definitions Alex Mastro
2026-01-14 18:57 ` [PATCH v3 2/3] vfio: selftests: Align BAR mmaps for efficient IOMMU mapping Alex Mastro
2026-01-14 18:57 ` [PATCH v3 3/3] vfio: selftests: Add vfio_dma_mapping_mmio_test Alex Mastro
2026-01-16 22:33 ` [PATCH v3 0/3] vfio: selftests: Add MMIO DMA mapping test David Matlack
2026-01-19 20:38 ` Alex Williamson
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=20260114-map-mmio-test-v3-0-44e036d95e64@fb.com \
--to=amastro@fb.com \
--cc=alex@shazbot.org \
--cc=dmatlack@google.com \
--cc=jgg@ziepe.ca \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=peterx@redhat.com \
--cc=shuah@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