public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Alex Williamson <alex.williamson@redhat.com>
To: Linus Torvalds <torvalds@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org,
	"kvm@vger.kernel.org" <kvm@vger.kernel.org>,
	"Andrew Morton" <akpm@linux-foundation.org>,
	"David Hildenbrand" <david@redhat.com>,
	lizhe.67@bytedance.com, "Cédric Le Goater" <clg@redhat.com>
Subject: [GIT PULL] VFIO updates for v6.18-rc1 part 2
Date: Wed, 8 Oct 2025 10:08:46 -0600	[thread overview]
Message-ID: <20251008100846.47bcedd1.alex.williamson@redhat.com> (raw)

Hi Linus,

Sorry for the two part pull request, this is mostly the DMA map/unmap
optimization series that we tried to get into v6.17, but made use of
the nth_page API that generated some objections.  That has since been
removed, but was stalled again by the page_to_section() to
memdesc_section() change, where I opt'd for this two part approach
rather than resolution buried in a merge commit since we saw it coming.
Thanks,

Alex

The following changes since commit fd94619c43360eb44d28bd3ef326a4f85c600a07:

  Merge tag 'zonefs-6.18-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/dlemoal/zonefs (2025-10-05 20:45:49 -0700)

are available in the Git repository at:

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

for you to fetch changes up to 451bb96328981808463405d436bd58de16dd967d:

  vfio: Dump migration features under debugfs (2025-10-06 11:22:48 -0600)

----------------------------------------------------------------
VFIO updates for v6.18-rc1 part 2

 - Optimizations for DMA map and unmap opertions through the type1
   vfio IOMMU backend.  This uses various means of batching and hints
   from the mm structures to improve efficiency and therefore
   performance, resulting in a significant speedup for huge page
   use cases. (Li Zhe)

 - Expose supported device migration features through debugfs.
   (Cédric Le Goater)

----------------------------------------------------------------
Cédric Le Goater (1):
      vfio: Dump migration features under debugfs

Li Zhe (5):
      mm: introduce num_pages_contiguous()
      vfio/type1: optimize vfio_pin_pages_remote()
      vfio/type1: batch vfio_find_vpfn() in function vfio_unpin_pages_remote()
      vfio/type1: introduce a new member has_rsvd for struct vfio_dma
      vfio/type1: optimize vfio_unpin_pages_remote()

 Documentation/ABI/testing/debugfs-vfio |   6 ++
 drivers/vfio/debugfs.c                 |  19 ++++++
 drivers/vfio/vfio_iommu_type1.c        | 112 ++++++++++++++++++++++++++-------
 include/linux/mm.h                     |   7 ++-
 include/linux/mm_inline.h              |  36 +++++++++++
 5 files changed, 158 insertions(+), 22 deletions(-)


             reply	other threads:[~2025-10-08 16:08 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-08 16:08 Alex Williamson [this message]
2025-10-08 18:48 ` [GIT PULL] VFIO updates for v6.18-rc1 part 2 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=20251008100846.47bcedd1.alex.williamson@redhat.com \
    --to=alex.williamson@redhat.com \
    --cc=akpm@linux-foundation.org \
    --cc=clg@redhat.com \
    --cc=david@redhat.com \
    --cc=kvm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lizhe.67@bytedance.com \
    --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