public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex@shazbot.org>
To: David Matlack <dmatlack@google.com>
Cc: Alex Mastro <amastro@fb.com>, Jason Gunthorpe <jgg@nvidia.com>,
	Josh Hilke <jrhilke@google.com>,
	kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-kselftest@vger.kernel.org,
	Raghavendra Rao Ananta <rananta@google.com>,
	Vipin Sharma <vipinsh@google.com>
Subject: Re: [PATCH v4 00/18] vfio: selftests: Support for multi-device tests
Date: Fri, 28 Nov 2025 12:44:44 -0700	[thread overview]
Message-ID: <20251128124444.2d6abe55.alex@shazbot.org> (raw)
In-Reply-To: <20251126231733.3302983-1-dmatlack@google.com>

On Wed, 26 Nov 2025 23:17:15 +0000
David Matlack <dmatlack@google.com> wrote:

> This series adds support for tests that use multiple devices, and adds
> one new test, vfio_pci_device_init_perf_test, which measures parallel
> device initialization time to demonstrate the improvement from commit
> e908f58b6beb ("vfio/pci: Separate SR-IOV VF dev_set").
> 
> This series also breaks apart the monolithic vfio_util.h and
> vfio_pci_device.c into separate files, to account for all the new code.
> This required quite a bit of code motion so the diffstat looks large.
> The final layout is more granular and provides a better separation of
> the IOMMU code from the device code.
> 
> Final layout:
> 
>   C files:
>     - tools/testing/selftests/vfio/lib/libvfio.c
>     - tools/testing/selftests/vfio/lib/iommu.c
>     - tools/testing/selftests/vfio/lib/iova_allocator.c
>     - tools/testing/selftests/vfio/lib/vfio_pci_device.c
>     - tools/testing/selftests/vfio/lib/vfio_pci_driver.c
> 
>   H files:
>    - tools/testing/selftests/vfio/lib/include/libvfio.h
>    - tools/testing/selftests/vfio/lib/include/libvfio/assert.h
>    - tools/testing/selftests/vfio/lib/include/libvfio/iommu.h
>    - tools/testing/selftests/vfio/lib/include/libvfio/iova_allocator.h
>    - tools/testing/selftests/vfio/lib/include/libvfio/vfio_pci_device.h
>    - tools/testing/selftests/vfio/lib/include/libvfio/vfio_pci_driver.h
> 
> Notably, vfio_util.h is now gone and replaced with libvfio.h.
> 
> This series is based on vfio/next plus Alex Mastro's series to add the
> IOVA allocator [1]. It should apply cleanly to vfio/next once Alex's
> series makes its way to vfio/next via Linus' tree.
> 
> This series can be found on GitHub:
> 
>   https://github.com/dmatlack/linux/tree/vfio/selftests/init_perf_test/v4
> 
> [1] https://lore.kernel.org/kvm/20251111-iova-ranges-v3-0-7960244642c5@fb.com/
> 
> Cc: Alex Mastro <amastro@fb.com>
> Cc: Jason Gunthorpe <jgg@nvidia.com>
> Cc: Josh Hilke <jrhilke@google.com>
> Cc: Raghavendra Rao Ananta <rananta@google.com>
> Cc: Vipin Sharma <vipinsh@google.com>
> 
> v4:

Applied to vfio next branch for v6.19.  Thanks,

Alex

      parent reply	other threads:[~2025-11-28 19:44 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-26 23:17 [PATCH v4 00/18] vfio: selftests: Support for multi-device tests David Matlack
2025-11-26 23:17 ` [PATCH v4 01/18] vfio: selftests: Move run.sh into scripts directory David Matlack
2025-11-26 23:17 ` [PATCH v4 02/18] vfio: selftests: Split run.sh into separate scripts David Matlack
2025-11-26 23:17 ` [PATCH v4 03/18] vfio: selftests: Allow passing multiple BDFs on the command line David Matlack
2025-11-26 23:17 ` [PATCH v4 04/18] vfio: selftests: Rename struct vfio_iommu_mode to iommu_mode David Matlack
2025-11-26 23:17 ` [PATCH v4 05/18] vfio: selftests: Introduce struct iommu David Matlack
2025-11-26 23:17 ` [PATCH v4 06/18] vfio: selftests: Support multiple devices in the same container/iommufd David Matlack
2025-11-26 23:17 ` [PATCH v4 07/18] vfio: selftests: Eliminate overly chatty logging David Matlack
2025-11-26 23:17 ` [PATCH v4 08/18] vfio: selftests: Prefix logs with device BDF where relevant David Matlack
2025-11-26 23:17 ` [PATCH v4 09/18] vfio: selftests: Upgrade driver logging to dev_err() David Matlack
2025-11-26 23:17 ` [PATCH v4 10/18] vfio: selftests: Rename struct vfio_dma_region to dma_region David Matlack
2025-11-26 23:17 ` [PATCH v4 11/18] vfio: selftests: Move IOMMU library code into iommu.c David Matlack
2025-11-26 23:17 ` [PATCH v4 12/18] vfio: selftests: Move IOVA allocator into iova_allocator.c David Matlack
2025-11-26 23:17 ` [PATCH v4 13/18] vfio: selftests: Stop passing device for IOMMU operations David Matlack
2025-11-26 23:17 ` [PATCH v4 14/18] vfio: selftests: Rename vfio_util.h to libvfio.h David Matlack
2025-11-26 23:17 ` [PATCH v4 15/18] vfio: selftests: Move vfio_selftests_*() helpers into libvfio.c David Matlack
2025-11-26 23:17 ` [PATCH v4 16/18] vfio: selftests: Split libvfio.h into separate header files David Matlack
2025-11-26 23:17 ` [PATCH v4 17/18] vfio: selftests: Eliminate INVALID_IOVA David Matlack
2025-11-26 23:17 ` [PATCH v4 18/18] vfio: selftests: Add vfio_pci_device_init_perf_test David Matlack
2025-11-28 19:44 ` Alex Williamson [this message]

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=20251128124444.2d6abe55.alex@shazbot.org \
    --to=alex@shazbot.org \
    --cc=amastro@fb.com \
    --cc=dmatlack@google.com \
    --cc=jgg@nvidia.com \
    --cc=jrhilke@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=rananta@google.com \
    --cc=vipinsh@google.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