From: "Michael S. Tsirkin" <mst@redhat.com>
To: Richard Henderson <richard.henderson@linaro.org>
Cc: Gavin Shan <gshan@redhat.com>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org, peterx@redhat.com,
alex@shazbot.org, peter.maydell@linaro.org, berrange@redhat.com,
philmd@oss.qualcomm.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 v2 1/2] system/memory: Use qemu_ram_{copy, move}() in ram device region accessors
Date: Mon, 15 Jun 2026 12:37:49 -0400 [thread overview]
Message-ID: <20260615123633-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20260615123354-mutt-send-email-mst@kernel.org>
On Mon, Jun 15, 2026 at 12:36:00PM -0400, Michael S. Tsirkin wrote:
> On Mon, Jun 15, 2026 at 08:17:14AM -0700, Richard Henderson wrote:
> > On 6/15/26 03:01, Gavin Shan wrote:
> > > +void qemu_ram_copy(void *dest, const void *src, size_t n)
> > > +{
> > > + if (HOST_UNALIGNED_MMIO_OK) {
> > > + switch (n) {
> > > + case 1:
> > > + __builtin_memcpy(dest, src, 1);
> > > + break;
> > > + case 2:
> > > + __builtin_memcpy(dest, src, 2);
> > > + break;
> > > + case 4:
> > > + __builtin_memcpy(dest, src, 4);
> > > + break;
> > > + case 8:
> > > + __builtin_memcpy(dest, src, 8);
> > > + break;
> > > + default:
> > > + memcpy(dest, src, n);
> > > + }
> > > + } else {
> > > + uintptr_t test, lsb;
> > > +
> > > + do {
> > > + test = (uintptr_t)dest | n;
> > > + lsb = test & -test;
> > > + switch (lsb) {
> >
> > Either assert n != 0 to start, or use while not do/while.
> > Because the body of the loop won't handle n == 0 correctly.
I think n!=0 performs better than a loop. Worth checking
asm though.
> > > + case 1:
> > > + *(uint8_t *)dest = *(uint8_t *)src;
> > > + src += 1;
> > > + dest += 1;
> > > + n -= 1;
> > > + break;
> > > + case 2:
> > > + *(uint16_t *)dest = *(uint16_t *)src;
> > > + src += 2;
> > > + dest += 2;
> > > + n -= 2;
> > > + break;
> > > + case 4:
> > > + *(uint32_t *)dest = *(uint32_t *)src;
> > > + src += 4;
> > > + dest += 4;
> > > + n -= 4;
> > > + break;
> > > + default:
> > > + *(uint64_t *)dest = *(uint64_t *)src;
> > > + src += 8;
> > > + dest += 8;
> > > + n -= 8;
> >
> > Use qatomic_set for the stores.
>
>
> Won't this do things like locked on x86?
Hmm I didn't check. It's relaxed - so no locked. Fine by me.
>
>
> >
> > src is not aligned, so except for case 1, you need ld{uw,l,q}_he_p.
>
> These just map back to memcpy. What is the point?
>
> > > +void qemu_ram_move(void *dest, const void *src, size_t n)
> > > +{
> > > + if (HOST_UNALIGNED_MMIO_OK) {
> > > + switch (n) {
> > > + case 1:
> > > + __builtin_memmove(dest, src, 1);
> > > + break;
> > > + case 2:
> > > + __builtin_memmove(dest, src, 2);
> > > + break;
> > > + case 4:
> > > + __builtin_memmove(dest, src, 4);
> > > + break;
> > > + case 8:
> > > + __builtin_memmove(dest, src, 8);
> > > + break;
> > > + default:
> > > + memmove(dest, src, n);
> > > + }
> > > + } else {
> > > + qemu_ram_copy(dest, src, n);
> > > + }
> > > +}
> >
> > The qemu_ram_copy implementation above does not work with overlapping blocks.
>
> IIUC copy is not supposed to. this is what move is for.
>
> >
> > r~
next prev parent reply other threads:[~2026-06-15 16:38 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-15 10:01 [PATCH v2 0/2] system/memory: Make ram device region directly accessible Gavin Shan
2026-06-15 10:01 ` [PATCH v2 1/2] system/memory: Use qemu_ram_{copy, move}() in ram device region accessors Gavin Shan
2026-06-15 10:57 ` Peter Maydell
2026-06-15 14:48 ` Michael S. Tsirkin
2026-06-15 14:56 ` Michael S. Tsirkin
2026-06-15 15:12 ` Peter Maydell
2026-06-15 19:24 ` Gavin Shan
2026-06-15 19:42 ` Michael S. Tsirkin
2026-06-15 21:31 ` Gavin Shan
2026-06-16 4:22 ` Gavin Shan
2026-06-16 4:36 ` Michael S. Tsirkin
2026-06-16 4:23 ` Michael S. Tsirkin
2026-06-16 4:48 ` Richard Henderson
2026-06-16 4:49 ` Michael S. Tsirkin
2026-06-16 4:55 ` Gavin Shan
2026-06-16 5:17 ` Michael S. Tsirkin
2026-06-16 5:21 ` Gavin Shan
2026-06-16 5:32 ` Michael S. Tsirkin
2026-06-16 4:59 ` Michael S. Tsirkin
2026-06-16 5:07 ` Gavin Shan
2026-06-16 5:25 ` Michael S. Tsirkin
2026-06-15 19:52 ` Michael S. Tsirkin
2026-06-15 15:17 ` Richard Henderson
2026-06-15 16:33 ` Gavin Shan
2026-06-15 17:03 ` Richard Henderson
2026-06-15 18:09 ` Gavin Shan
2026-06-15 18:33 ` Richard Henderson
2026-06-15 19:40 ` Michael S. Tsirkin
2026-06-16 4:18 ` Gavin Shan
2026-06-15 16:35 ` Michael S. Tsirkin
2026-06-15 16:37 ` Michael S. Tsirkin [this message]
2026-06-15 17:05 ` Richard Henderson
2026-06-15 10:01 ` [PATCH v2 2/2] system/memory: Make ram device region directly accessible Gavin Shan
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=20260615123633-mutt-send-email-mst@kernel.org \
--to=mst@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=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=peterx@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox