From: Peter Xu <peterx@redhat.com>
To: Gavin Shan <gshan@redhat.com>
Cc: qemu-arm@nongnu.org, qemu-devel@nongnu.org, mst@redhat.com,
philmd@oss.qualcomm.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 v4 1/3] system/memory: Use memmove() for directly accessible regions
Date: Mon, 27 Jul 2026 10:03:41 -0400 [thread overview]
Message-ID: <amdlPQtJNoJV3e_o@x1.local> (raw)
In-Reply-To: <20260727032649.145381-2-gshan@redhat.com>
On Mon, Jul 27, 2026 at 01:26:47PM +1000, 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 Xu <peterx@redhat.com>
--
Peter Xu
next prev parent reply other threads:[~2026-07-27 14:04 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-27 3:26 [PATCH v4 0/3] system/memory: Make ram device region directly accessible Gavin Shan
2026-07-27 3:26 ` [PATCH v4 1/3] system/memory: Use memmove() for directly accessible regions Gavin Shan
2026-07-27 10:51 ` Peter Maydell
2026-07-27 14:03 ` Peter Xu [this message]
2026-07-27 3:26 ` [PATCH v4 2/3] system/memory: Use qemu_ram_move() " Gavin Shan
2026-07-27 12:51 ` Peter Maydell
2026-07-27 13:52 ` Philippe Mathieu-Daudé
2026-07-27 14:02 ` Peter Xu
2026-07-27 3:26 ` [PATCH v4 3/3] system/memory: Make ram device region directly accessible Gavin Shan
2026-07-27 12:07 ` Peter Maydell
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=amdlPQtJNoJV3e_o@x1.local \
--to=peterx@redhat.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=philmd@mailo.com \
--cc=philmd@oss.qualcomm.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.