On Sun, Nov 15, 2026 at 3:19 PM Jason Gunthorpe <[email protected]> wrote: > > On Thu, Nov 12, 2026 at 01:47:03PM -0800, David Matlack wrote: > > On Thu Nov 12, 2026 at 12:35 PM PST, Alex Mastro wrote: > > > Hey David, > > > > > > On Wed, Nov 11, 2026 at 07:24:04PM +0000, David Matlack wrote: > > > > > >> Is requiring userspace to re-issue IOMMU_IOAS_MAP_FILE the expected > > >> uAPI behavior? > > Yes. Even if we wanted to the locking is doesn't allow trying to do it > automatically. > > > The way I designed the P2P selftest support requires 2 things: > > > > (A) initiator: A device that has a VFIO selftests driver. > > (B) target: A device that can provide a memory BAR > > (vfio_pci_find_mem_bar()). > > > > So far I haven't found a single device that can do both. But you are > > right that theoretically a single device could satisfy both > > requirements. > > mlx5 can do both
Looks like GPUs and NVMe can do both as well. How would we implement vfio_pci_find_mem_bar() for mlx5? BTW for the target device, by "a memory BAR" I meant "a region of a memory BAR that behaves like normal RAM". Sorry that was not clear.
