From: "Cédric Le Goater" <clg@redhat.com>
To: qemu-devel@nongnu.org
Cc: "Alex Williamson" <alex.williamson@redhat.com>,
"Cédric Le Goater" <clg@redhat.com>
Subject: [PULL 0/5] vfio queue
Date: Fri, 3 Oct 2025 12:33:23 +0200 [thread overview]
Message-ID: <20251003103328.1864910-1-clg@redhat.com> (raw)
The following changes since commit 29b77c1a2db2d796bc3847852a5c8dc2a1e6e83b:
Merge tag 'rust-ci-pull-request' of https://gitlab.com/marcandre.lureau/qemu into staging (2025-09-30 09:29:38 -0700)
are available in the Git repository at:
https://github.com/legoater/qemu/ tags/pull-vfio-20251003
for you to fetch changes up to f0b52aa08ab0868c18d881381a8fda4b59b37517:
hw/vfio: Use uint64_t for IOVA mapping size in vfio_container_dma_*map (2025-10-02 10:41:23 +0200)
----------------------------------------------------------------
vfio queue:
* Remove workaround for kernel DMA unmap overflow
* Remove invalid uses of ram_addr_t type
----------------------------------------------------------------
Cédric Le Goater (1):
vfio: Remove workaround for kernel DMA unmap overflow bug
Philippe Mathieu-Daudé (4):
system/iommufd: Use uint64_t type for IOVA mapping size
hw/vfio: Reorder vfio_container_query_dirty_bitmap() trace format
hw/vfio: Avoid ram_addr_t in vfio_container_query_dirty_bitmap()
hw/vfio: Use uint64_t for IOVA mapping size in vfio_container_dma_*map
include/hw/vfio/vfio-container.h | 13 +++++++------
include/hw/vfio/vfio-cpr.h | 2 +-
include/system/iommufd.h | 6 +++---
backends/iommufd.c | 6 +++---
hw/vfio-user/container.c | 4 ++--
hw/vfio/container-legacy.c | 28 +++++-----------------------
hw/vfio/container.c | 15 ++++++++-------
hw/vfio/cpr-legacy.c | 2 +-
hw/vfio/iommufd.c | 6 +++---
hw/vfio/listener.c | 18 +++++++++---------
hw/vfio/trace-events | 7 +++----
11 files changed, 45 insertions(+), 62 deletions(-)
next reply other threads:[~2025-10-03 10:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-03 10:33 Cédric Le Goater [this message]
2025-10-03 10:33 ` [PULL 1/5] vfio: Remove workaround for kernel DMA unmap overflow bug Cédric Le Goater
2025-10-03 10:33 ` [PULL 2/5] system/iommufd: Use uint64_t type for IOVA mapping size Cédric Le Goater
2025-10-03 10:33 ` [PULL 3/5] hw/vfio: Reorder vfio_container_query_dirty_bitmap() trace format Cédric Le Goater
2025-10-03 10:33 ` [PULL 4/5] hw/vfio: Avoid ram_addr_t in vfio_container_query_dirty_bitmap() Cédric Le Goater
2025-10-03 10:33 ` [PULL 5/5] hw/vfio: Use uint64_t for IOVA mapping size in vfio_container_dma_*map Cédric Le Goater
2025-10-03 17:33 ` [PULL 0/5] vfio queue Richard Henderson
-- strict thread matches above, loose matches on Subject: below --
2025-07-29 6:26 Cédric Le Goater
2025-07-29 16:59 ` Stefan Hajnoczi
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=20251003103328.1864910-1-clg@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).