mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Alex Williamson <alex@shazbot.org>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	Alex Mastro <amastro@fb.com>, David Matlack <dmatlack@google.com>
Subject: [GIT PULL] VFIO fixes for v6.18-rc6
Date: Thu, 13 Nov 2025 16:08:31 -0700	[thread overview]
Message-ID: <20251113160831.775d61dd.alex@shazbot.org> (raw)

Hi Linus,

Here are a few last fixes for the new vfio selftests for v6.18.  This
hopefully starts us off with a good precedent that the tests will
generally pass by removing some assumptions about the IOMMU address
width.  Thanks,

Alex

The following changes since commit 6146a0f1dfae5d37442a9ddcba012add260bceb0:

  Linux 6.18-rc4 (2025-11-02 11:28:02 -0800)

are available in the Git repository at:

  https://github.com/awilliam/linux-vfio.git tags/vfio-v6.18-rc6

for you to fetch changes up to d323ad739666761646048fca587734f4ae64f2c8:

  vfio: selftests: replace iova=vaddr with allocated iovas (2025-11-12 08:04:42 -0700)

----------------------------------------------------------------
VFIO fixes for v6.18-rc6

 - Fix vfio selftests to remove the expectation that the IOMMU
   supports a 64-bit IOVA space.  These manifest both in the original
   set of tests introduced this development cycle in identity mapping
   the IOVA to buffer virtual address space, as well as the more
   recent boundary testing.  Implement facilities for collecting the
   valid IOVA ranges from the backend, implement a simple IOVA
   allocator, and use the information for determining extents.
   (Alex Mastro)

----------------------------------------------------------------
Alex Mastro (4):
      vfio: selftests: add iova range query helpers
      vfio: selftests: fix map limit tests to use last available iova
      vfio: selftests: add iova allocator
      vfio: selftests: replace iova=vaddr with allocated iovas

 .../testing/selftests/vfio/lib/include/vfio_util.h |  19 +-
 tools/testing/selftests/vfio/lib/vfio_pci_device.c | 246 ++++++++++++++++++++-
 .../testing/selftests/vfio/vfio_dma_mapping_test.c |  20 +-
 .../testing/selftests/vfio/vfio_pci_driver_test.c  |  12 +-
 4 files changed, 288 insertions(+), 9 deletions(-)

             reply	other threads:[~2025-11-13 23:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-13 23:08 Alex Williamson [this message]
2025-11-14  1:05 ` pr-tracker-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=20251113160831.775d61dd.alex@shazbot.org \
    --to=alex@shazbot.org \
    --cc=amastro@fb.com \
    --cc=dmatlack@google.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=torvalds@linux-foundation.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

all inboxes | Powered by JetHome®