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>
Subject: Re: [PULL 00/16] vfio queue
Date: Tue, 23 Jul 2024 17:13:53 +0200	[thread overview]
Message-ID: <aba2bede-c727-4def-8cad-cb0daedd708d@redhat.com> (raw)
In-Reply-To: <20240723140019.387786-1-clg@redhat.com>

On 7/23/24 16:00, Cédric Le Goater wrote:
> The following changes since commit 6af69d02706c821797802cfd56acdac13a7c9422:
> 
>    Merge tag 'nvme-next-pull-request' of https://gitlab.com/birkelund/qemu into staging (2024-07-23 13:55:45 +1000)
> 
> are available in the Git repository at:
> 
>    https://github.com/legoater/qemu/ tags/pull-vfio-20240723
> 
> for you to fetch changes up to 6ac9efe6805af60de14481fdde7d340080d38324:
> 
>    vfio/common: Allow disabling device dirty page tracking (2024-07-23 11:10:10 +0200)
> 
> ----------------------------------------------------------------
> vfio queue:
> 
> * IOMMUFD Dirty Tracking support
> * Fix for a possible SEGV in IOMMU type1 container
> * Dropped initialization of host IOMMU device with mdev devices

There is a problem with an email address in patch 13 :

    Reviewed-by: Cédric Le Goater <clg@redhat.co>

I will repush an resend.


Thanks,

C.




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

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-23 14:00 [PULL 00/16] vfio queue Cédric Le Goater
2024-07-23 14:00 ` [PULL 01/16] hw/vfio/container: Fix SIGSEV on vfio_container_instance_finalize() Cédric Le Goater
2024-07-23 14:00 ` [PULL 02/16] vfio/pci: Extract mdev check into an helper Cédric Le Goater
2024-07-23 14:00 ` [PULL 03/16] vfio/iommufd: Don't initialize nor set a HOST_IOMMU_DEVICE with mdev Cédric Le Goater
2024-07-23 14:00 ` [PULL 04/16] backends/iommufd: Extend iommufd_backend_get_device_info() to fetch HW capabilities Cédric Le Goater
2024-07-23 14:00 ` [PULL 05/16] vfio/iommufd: Return errno in iommufd_cdev_attach_ioas_hwpt() Cédric Le Goater
2024-07-23 14:00 ` [PULL 06/16] vfio/ap: Don't initialize HOST_IOMMU_DEVICE with mdev Cédric Le Goater
2024-07-23 14:00 ` [PULL 07/16] vfio/ccw: " Cédric Le Goater
2024-07-23 14:00 ` [PULL 08/16] vfio/iommufd: Introduce auto domain creation Cédric Le Goater
2024-07-23 14:00 ` [PULL 09/16] vfio/{iommufd,container}: Remove caps::aw_bits Cédric Le Goater
2024-07-23 14:00 ` [PULL 10/16] vfio/iommufd: Add hw_caps field to HostIOMMUDeviceCaps Cédric Le Goater
2024-07-23 14:00 ` [PULL 11/16] vfio/{iommufd, container}: Invoke HostIOMMUDevice::realize() during attach_device() Cédric Le Goater
2024-07-23 14:00 ` [PULL 12/16] vfio/iommufd: Probe and request hwpt dirty tracking capability Cédric Le Goater
2024-07-23 14:00 ` [PULL 13/16] vfio/iommufd: Implement VFIOIOMMUClass::set_dirty_tracking support Cédric Le Goater
2024-07-23 15:13 ` Cédric Le Goater [this message]
  -- strict thread matches above, loose matches on Subject: below --
2025-06-05  8:42 [PULL 00/16] vfio queue Cédric Le Goater
2025-06-05 19:00 ` Stefan Hajnoczi
2023-06-30  5:22 Cédric Le Goater
2023-06-30  9:55 ` 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=aba2bede-c727-4def-8cad-cb0daedd708d@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).