From: "Cédric Le Goater" <clg@redhat.com>
To: John Levon <john.levon@nutanix.com>, qemu-devel@nongnu.org
Cc: Alex Williamson <alex.williamson@redhat.com>,
Thanos Makatos <thanos.makatos@nutanix.com>,
Thomas Huth <thuth@redhat.com>,
Matthew Rosato <mjrosato@linux.ibm.com>,
Eric Farman <farman@linux.ibm.com>,
qemu-stable@nongnu.org, qemu-s390x@nongnu.org,
Mario Casquero <mcasquer@redhat.com>
Subject: Re: [PATCH 0/2] Fixes for vfio region cache
Date: Wed, 15 Oct 2025 14:06:40 +0200 [thread overview]
Message-ID: <1c3c13c6-cb2d-4254-b4c4-a69e44dfd89a@redhat.com> (raw)
In-Reply-To: <07ac3b8f-c6d0-43e4-a41d-23a6abbe296d@redhat.com>
On 10/14/25 21:20, Cédric Le Goater wrote:
> + Mario
>
> On 10/14/25 17:12, John Levon wrote:
>>
>>
>> John Levon (2):
>> vfio: rename field to "num_initial_regions"
>> vfio: only check region info cache for initial regions
>>
>> include/hw/vfio/vfio-device.h | 2 +-
>> hw/vfio-user/device.c | 2 +-
>> hw/vfio/ccw.c | 4 ++--
>> hw/vfio/device.c | 39 ++++++++++++++++++++++-------------
>> hw/vfio/iommufd.c | 3 ++-
>> hw/vfio/pci.c | 4 ++--
>> 6 files changed, 33 insertions(+), 21 deletions(-)
>>
>
> That was quick ! Thanks John. I will build a version based
> on upstream for internal testing.
All good. Thanks to Mario.
Applied to vfio-next.
C.
prev parent reply other threads:[~2025-10-15 12:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-14 15:12 [PATCH 0/2] Fixes for vfio region cache John Levon
2025-10-14 15:12 ` [PATCH 1/2] vfio: rename field to "num_initial_regions" John Levon
2025-10-14 19:17 ` Cédric Le Goater
2025-10-14 15:12 ` [PATCH 2/2] vfio: only check region info cache for initial regions John Levon
2025-10-14 19:20 ` Cédric Le Goater
2025-10-14 15:24 ` [PATCH 0/2] Fixes for vfio region cache Alex Williamson
2025-10-14 19:20 ` Cédric Le Goater
2025-10-15 12:06 ` Cédric Le Goater [this message]
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=1c3c13c6-cb2d-4254-b4c4-a69e44dfd89a@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=farman@linux.ibm.com \
--cc=john.levon@nutanix.com \
--cc=mcasquer@redhat.com \
--cc=mjrosato@linux.ibm.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=qemu-stable@nongnu.org \
--cc=thanos.makatos@nutanix.com \
--cc=thuth@redhat.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).