From: "Cédric Le Goater" <clg@redhat.com>
To: John Levon <john.levon@nutanix.com>, qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Halil Pasic" <pasic@linux.ibm.com>,
"Tomita Moeko" <tomitamoeko@gmail.com>,
"Matthew Rosato" <mjrosato@linux.ibm.com>,
"Stefano Garzarella" <sgarzare@redhat.com>,
"Alex Williamson" <alex.williamson@redhat.com>,
"Peter Xu" <peterx@redhat.com>, "Thomas Huth" <thuth@redhat.com>,
"Tony Krowiak" <akrowiak@linux.ibm.com>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Eric Farman" <farman@linux.ibm.com>,
"David Hildenbrand" <david@redhat.com>,
qemu-s390x@nongnu.org, "Jason Herne" <jjherne@linux.ibm.com>
Subject: Re: [PATCH v3 00/15] vfio: preparation for vfio-user
Date: Fri, 9 May 2025 12:24:39 +0200 [thread overview]
Message-ID: <92196d3c-4bb5-4b88-9d8b-38f2c7ebb385@redhat.com> (raw)
In-Reply-To: <20250507152020.1254632-1-john.levon@nutanix.com>
On 5/7/25 17:20, John Levon wrote:
> Hi, this series is against the vfio-next tree:
> https://github.com/legoater/qemu/commits/vfio-next
>
> The series contains patches to vfio to prepare for the vfio-user
> implementation. A previous version of these patches can be found at
> https://patchew.org/QEMU/20250430194003.2793823-1-john.levon@nutanix.com/
>
> The changes have been rebased on vfio-next, and include changes from previous
> series code review comments.
>
> An old version of the full vfio-user series can be found at
> https://lore.kernel.org/all/7dd34008-e0f1-4eed-a77e-55b1f68fbe69@redhat.com/T/
> ("[PATCH v8 00/28] vfio-user client"). Please see that series for justification
> and context.
>
> thanks
> john
>
> John Levon (15):
> vfio: add vfio_device_prepare()
> vfio: add vfio_device_unprepare()
> vfio: add vfio_attach_device_by_iommu_type()
> vfio: add vfio_device_get_irq_info() helper
> vfio: consistently handle return value for helpers
> vfio: add strread/writeerror()
> vfio: add vfio_pci_config_space_read/write()
> vfio: add unmap_all flag to DMA unmap callback
> vfio: implement unmap all for DMA unmap callbacks
> vfio: add device IO ops vector
> vfio: add region info cache
> vfio: add read/write to device IO ops vector
> vfio: add vfio-pci-base class
> vfio/container: pass listener_begin/commit callbacks
> vfio/container: pass MemoryRegion to DMA operations
>
> hw/vfio/pci.h | 10 +-
> include/hw/vfio/vfio-container-base.h | 21 ++-
> include/hw/vfio/vfio-device.h | 82 ++++++++
> include/system/memory.h | 4 +-
> hw/vfio/ap.c | 19 +-
> hw/vfio/ccw.c | 25 ++-
> hw/vfio/container-base.c | 14 +-
> hw/vfio/container.c | 62 ++++---
> hw/vfio/device.c | 183 ++++++++++++++++--
> hw/vfio/igd.c | 10 +-
> hw/vfio/iommufd.c | 35 ++--
> hw/vfio/listener.c | 82 +++++---
> hw/vfio/pci.c | 257 ++++++++++++++++----------
> hw/vfio/platform.c | 6 +-
> hw/vfio/region.c | 19 +-
> hw/virtio/vhost-vdpa.c | 2 +-
> system/memory.c | 7 +-
> 17 files changed, 603 insertions(+), 235 deletions(-)
>
I am waiting for an update of patch 12 to apply 01-14 to vfio-next.
patch 15 should be addressed independently.
Thanks,
C.
next prev parent reply other threads:[~2025-05-09 10:25 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-07 15:20 [PATCH v3 00/15] vfio: preparation for vfio-user John Levon
2025-05-07 15:20 ` [PATCH v3 01/15] vfio: add vfio_device_prepare() John Levon
2025-05-07 15:20 ` [PATCH v3 02/15] vfio: add vfio_device_unprepare() John Levon
2025-05-07 15:20 ` [PATCH v3 03/15] vfio: add vfio_attach_device_by_iommu_type() John Levon
2025-05-07 15:20 ` [PATCH v3 04/15] vfio: add vfio_device_get_irq_info() helper John Levon
2025-05-07 15:20 ` [PATCH v3 05/15] vfio: consistently handle return value for helpers John Levon
2025-05-07 15:20 ` [PATCH v3 06/15] vfio: add strread/writeerror() John Levon
2025-05-09 10:05 ` Cédric Le Goater
2025-05-07 15:20 ` [PATCH v3 07/15] vfio: add vfio_pci_config_space_read/write() John Levon
2025-05-07 15:20 ` [PATCH v3 08/15] vfio: add unmap_all flag to DMA unmap callback John Levon
2025-05-09 10:07 ` Cédric Le Goater
2025-05-07 15:20 ` [PATCH v3 09/15] vfio: implement unmap all for DMA unmap callbacks John Levon
2025-05-09 10:08 ` Cédric Le Goater
2025-05-07 15:20 ` [PATCH v3 10/15] vfio: add device IO ops vector John Levon
2025-05-09 10:09 ` Cédric Le Goater
2025-05-07 15:20 ` [PATCH v3 11/15] vfio: add region info cache John Levon
2025-05-09 10:09 ` Cédric Le Goater
2025-05-07 15:20 ` [PATCH v3 12/15] vfio: add read/write to device IO ops vector John Levon
2025-05-09 10:14 ` Cédric Le Goater
2025-05-09 10:32 ` John Levon
2025-05-07 15:20 ` [PATCH v3 13/15] vfio: add vfio-pci-base class John Levon
2025-05-09 10:14 ` Cédric Le Goater
2025-05-07 15:20 ` [PATCH v3 14/15] vfio/container: pass listener_begin/commit callbacks John Levon
2025-05-07 15:20 ` [PATCH v3 15/15] vfio/container: pass MemoryRegion to DMA operations John Levon
2025-05-09 10:22 ` Cédric Le Goater
2025-05-09 10:24 ` Cédric Le Goater [this message]
2025-05-09 12:45 ` [PATCH v3 00/15] vfio: preparation for vfio-user Cédric Le Goater
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=92196d3c-4bb5-4b88-9d8b-38f2c7ebb385@redhat.com \
--to=clg@redhat.com \
--cc=akrowiak@linux.ibm.com \
--cc=alex.williamson@redhat.com \
--cc=david@redhat.com \
--cc=farman@linux.ibm.com \
--cc=jjherne@linux.ibm.com \
--cc=john.levon@nutanix.com \
--cc=mjrosato@linux.ibm.com \
--cc=mst@redhat.com \
--cc=pasic@linux.ibm.com \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=sgarzare@redhat.com \
--cc=thuth@redhat.com \
--cc=tomitamoeko@gmail.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;
as well as URLs for NNTP newsgroup(s).