From: "Cédric Le Goater" <clg@redhat.com>
To: Steven Sistare <steven.sistare@oracle.com>,
John Levon <john.levon@nutanix.com>,
qemu-devel@nongnu.org
Cc: Alex Williamson <alex.williamson@redhat.com>,
John Johnson <john.g.johnson@oracle.com>,
Jagannathan Raman <jag.raman@oracle.com>,
Elena Ufimtseva <elena.ufimtseva@oracle.com>
Subject: Re: [PATCH] vfio/container: pass MemoryRegion to DMA operations
Date: Fri, 23 May 2025 08:24:25 +0200 [thread overview]
Message-ID: <7570ec21-9f28-4a07-b8fc-e3775683c3be@redhat.com> (raw)
In-Reply-To: <29454dcd-2eb7-4cef-83f2-659fdddeacf4@oracle.com>
On 5/22/25 19:30, Steven Sistare wrote:
> On 5/22/2025 1:20 PM, Cédric Le Goater wrote:
>> On 5/21/25 23:55, John Levon wrote:
>>> Pass through the MemoryRegion to DMA operation handlers of vfio
>>> containers. The vfio-user container will need this later, to translate
>>> the vaddr into an offset for the dma map vfio-user message; CPR will
>>> also will need this.
>>>
>>> Originally-by: John Johnson <john.g.johnson@oracle.com>
>>> Signed-off-by: Jagannathan Raman <jag.raman@oracle.com>
>>> Signed-off-by: Elena Ufimtseva <elena.ufimtseva@oracle.com>
>>> Signed-off-by: John Levon <john.levon@nutanix.com>
>>> ---
>>> include/hw/vfio/vfio-container-base.h | 9 +++++----
>>> hw/vfio/container-base.c | 4 ++--
>>> hw/vfio/container.c | 3 ++-
>>> hw/vfio/iommufd.c | 3 ++-
>>> hw/vfio/listener.c | 6 +++---
>>> 5 files changed, 14 insertions(+), 11 deletions(-)
>>
>> Steven,
>>
>> Can you base the live update series on this patch ?
>
> Yes, its already on my todo list for V4.
Could you add your R-b ?
Thanks,
C.
next prev parent reply other threads:[~2025-05-23 6:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-21 21:55 [PATCH] vfio/container: pass MemoryRegion to DMA operations John Levon
2025-05-21 21:58 ` John Levon
2025-05-22 17:20 ` Cédric Le Goater
2025-05-22 17:30 ` Steven Sistare
2025-05-23 6:24 ` Cédric Le Goater [this message]
2025-05-23 14:47 ` Steven Sistare
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=7570ec21-9f28-4a07-b8fc-e3775683c3be@redhat.com \
--to=clg@redhat.com \
--cc=alex.williamson@redhat.com \
--cc=elena.ufimtseva@oracle.com \
--cc=jag.raman@oracle.com \
--cc=john.g.johnson@oracle.com \
--cc=john.levon@nutanix.com \
--cc=qemu-devel@nongnu.org \
--cc=steven.sistare@oracle.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).