qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
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 v2 00/16] vfio queue
Date: Tue, 23 Jul 2024 17:20:34 +0200	[thread overview]
Message-ID: <20240723152035.409000-1-clg@redhat.com> (raw)

The following changes since commit 3cce8bd4d737f2ca688bbdcb92cd5cc683245bbd:

  Merge tag 'ui-pull-request' of https://gitlab.com/marcandre.lureau/qemu into staging (2024-07-23 15:23:05 +1000)

are available in the Git repository at:

  https://github.com/legoater/qemu/ tags/pull-vfio-20240723-1

for you to fetch changes up to 30b9167785177ac43d11b881fe321918124aeb88:

  vfio/common: Allow disabling device dirty page tracking (2024-07-23 17:14:53 +0200)

Changes in v2:

  - Rebased  
  - Fixed bogus email in "vfio/iommufd: Implement
    VFIOIOMMUClass::query_dirty_bitmap support"

----------------------------------------------------------------
vfio queue:

* IOMMUFD Dirty Tracking support
* Fix for a possible SEGV in IOMMU type1 container
* Dropped initialization of host IOMMU device with mdev devices

----------------------------------------------------------------
Eric Auger (1):
      hw/vfio/container: Fix SIGSEV on vfio_container_instance_finalize()

Joao Martins (13):
      vfio/pci: Extract mdev check into an helper
      vfio/iommufd: Don't initialize nor set a HOST_IOMMU_DEVICE with mdev
      backends/iommufd: Extend iommufd_backend_get_device_info() to fetch HW capabilities
      vfio/iommufd: Return errno in iommufd_cdev_attach_ioas_hwpt()
      vfio/iommufd: Introduce auto domain creation
      vfio/{iommufd,container}: Remove caps::aw_bits
      vfio/iommufd: Add hw_caps field to HostIOMMUDeviceCaps
      vfio/{iommufd, container}: Invoke HostIOMMUDevice::realize() during attach_device()
      vfio/iommufd: Probe and request hwpt dirty tracking capability
      vfio/iommufd: Implement VFIOIOMMUClass::set_dirty_tracking support
      vfio/iommufd: Implement VFIOIOMMUClass::query_dirty_bitmap support
      vfio/migration: Don't block migration device dirty tracking is unsupported
      vfio/common: Allow disabling device dirty page tracking

Zhenzhong Duan (2):
      vfio/ap: Don't initialize HOST_IOMMU_DEVICE with mdev
      vfio/ccw: Don't initialize HOST_IOMMU_DEVICE with mdev

 include/hw/vfio/vfio-common.h      |  15 +++
 include/sysemu/host_iommu_device.h |   5 +-
 include/sysemu/iommufd.h           |  13 ++-
 backends/iommufd.c                 |  89 ++++++++++++++++-
 hw/vfio/ap.c                       |   3 +
 hw/vfio/ccw.c                      |   3 +
 hw/vfio/common.c                   |  17 ++--
 hw/vfio/container.c                |  10 +-
 hw/vfio/helpers.c                  |  25 +++++
 hw/vfio/iommufd.c                  | 196 +++++++++++++++++++++++++++++++++++--
 hw/vfio/migration.c                |  12 ++-
 hw/vfio/pci.c                      |  26 ++---
 backends/trace-events              |   3 +
 13 files changed, 377 insertions(+), 40 deletions(-)



             reply	other threads:[~2024-07-23 15:21 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-23 15:20 Cédric Le Goater [this message]
2024-07-24  5:39 ` [PULL v2 00/16] vfio queue Richard Henderson

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=20240723152035.409000-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).