From: "Philippe Mathieu-Daudé" <philmd@oss.qualcomm.com>
To: Gavin Shan <gshan@redhat.com>, qemu-arm@nongnu.org
Cc: qemu-devel@nongnu.org, peterx@redhat.com, mst@redhat.com,
peter.maydell@linaro.org, richard.henderson@linaro.org,
alex@shazbot.org, berrange@redhat.com, philmd@mailo.com,
david@kernel.org, clg@redhat.com, pbonzini@redhat.com,
phrdina@redhat.com, jugraham@redhat.com,
liugang24219@sangfor.com.cn, dinghui@sangfor.com.cn,
shan.gavin@gmail.com
Subject: Re: [PATCH v5 1/3] system/memory: Use memmove() for directly accessible regions
Date: Tue, 28 Jul 2026 18:07:17 +0200 [thread overview]
Message-ID: <fb08095d-b70b-4565-95dc-a328afc6b04f@oss.qualcomm.com> (raw)
In-Reply-To: <20260728031731.286666-2-gshan@redhat.com>
On 28/7/26 05:17, Gavin Shan wrote:
> Similar to what's done in commit 4a73aee88140 ("softmmu: Use memmove in
> flatview_write_continue"), there are more sites where the overlapping
> source and destination buffer are allowed for the directly accessible
> regions. Use memmove() in those sites, listed as below.
>
> hw/remote/vfio-user-obj.c::vfu_object_mr_rw
> include/system/memory.h::address_space_read
> system/physmem.c::flatview_read_continue_step
>
> Signed-off-by: Gavin Shan <gshan@redhat.com>
> Reviewed-by: Peter Maydell <peter.maydell@linaro.org>
> Reviewed-by: Peter Xu <peterx@redhat.com>
> ---
> hw/remote/vfio-user-obj.c | 4 ++--
> include/system/memory.h | 2 +-
> system/physmem.c | 2 +-
> 3 files changed, 4 insertions(+), 4 deletions(-)
Reviewed-by: Philippe Mathieu-Daudé <philmd@oss.qualcomm.com>
next prev parent reply other threads:[~2026-07-28 16:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-28 3:17 [PATCH v5 0/3] system/memory: Make ram device region directly accessible Gavin Shan
2026-07-28 3:17 ` [PATCH v5 1/3] system/memory: Use memmove() for directly accessible regions Gavin Shan
2026-07-28 16:07 ` Philippe Mathieu-Daudé [this message]
2026-07-28 3:17 ` [PATCH v5 2/3] system/memory: Use qemu_ram_move() " Gavin Shan
2026-07-29 22:35 ` Michael S. Tsirkin
2026-07-30 6:26 ` Gavin Shan
2026-07-30 9:24 ` Peter Maydell
2026-07-30 10:27 ` Michael S. Tsirkin
2026-07-30 10:34 ` Peter Maydell
2026-07-30 10:50 ` Cédric Le Goater
2026-07-31 0:14 ` Gavin Shan
2026-07-28 3:17 ` [PATCH v5 3/3] system/memory: Make ram device region directly accessible Gavin Shan
2026-07-28 15:19 ` [PATCH v5 0/3] " Peter Xu
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=fb08095d-b70b-4565-95dc-a328afc6b04f@oss.qualcomm.com \
--to=philmd@oss.qualcomm.com \
--cc=alex@shazbot.org \
--cc=berrange@redhat.com \
--cc=clg@redhat.com \
--cc=david@kernel.org \
--cc=dinghui@sangfor.com.cn \
--cc=gshan@redhat.com \
--cc=jugraham@redhat.com \
--cc=liugang24219@sangfor.com.cn \
--cc=mst@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--cc=philmd@mailo.com \
--cc=phrdina@redhat.com \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=shan.gavin@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.