From: oleksii.kurochko@gmail.com
To: Jan Beulich <jbeulich@suse.com>
Cc: Alistair Francis <alistair.francis@wdc.com>,
Bob Eshleman <bobbyeshleman@gmail.com>,
Connor Davis <connojdavis@gmail.com>,
Andrew Cooper <andrew.cooper3@citrix.com>,
Julien Grall <julien@xen.org>,
Stefano Stabellini <sstabellini@kernel.org>,
xen-devel@lists.xenproject.org
Subject: Re: [PATCH v7 2/8] xen/riscv: allow write_atomic() to work with non-scalar types
Date: Mon, 16 Sep 2024 10:54:54 +0200 [thread overview]
Message-ID: <8a2ca782f0b059f58107a9545a63cce59a118a41.camel@gmail.com> (raw)
In-Reply-To: <441d53b7-71ee-483c-8d46-b3f7efeda023@suse.com>
On Mon, 2024-09-16 at 08:25 +0200, Jan Beulich wrote:
> On 13.09.2024 17:57, Oleksii Kurochko wrote:
> > Update the defintion of write_atomic() to support non-scalar types,
> > aligning it with the behavior of read_atomic().
>
> "Aligning" would imo imply yet more similarity. Types are different,
> names are different. How about "bringing it closer to"?
>
> > --- a/xen/arch/riscv/include/asm/atomic.h
> > +++ b/xen/arch/riscv/include/asm/atomic.h
> > @@ -69,10 +69,11 @@ static always_inline void
> > _write_atomic(volatile void *p,
> > }
> > }
> >
> > -#define write_atomic(p, x) \
> > -({ \
> > - typeof(*(p)) x_ = (x); \
> > - _write_atomic(p, x_, sizeof(*(p))); \
> > +#define write_atomic(p,
> > x) \
> > +({
> > \
> > + union { typeof(*(p)) v; unsigned long v_ul; } x_ = { .v_ul =
> > 0UL }; \
> > + x_.v =
> > (x); \
> > + _write_atomic(p, x_.v_ul,
> > sizeof(*(p))); \
>
> v_ul is an odd name for my taste. Why not just ul, which is closer to
> read_atomic()'s c? Preferably with the adjustments (which I guess
> could
> be done while committing, so long as you agree)
I will be happy with that.
> Acked-by: Jan Beulich <jbeulich@suse.com>
Thanks.
~ Oleksii
next prev parent reply other threads:[~2024-09-16 8:55 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 15:57 [PATCH v7 0/8] device tree mapping Oleksii Kurochko
2024-09-13 15:57 ` [PATCH v7 1/8] xen/riscv: use {read,write}{b,w,l,q}_cpu() to define {read,write}_atomic() Oleksii Kurochko
2024-09-16 6:17 ` Jan Beulich
2024-09-13 15:57 ` [PATCH v7 2/8] xen/riscv: allow write_atomic() to work with non-scalar types Oleksii Kurochko
2024-09-16 6:25 ` Jan Beulich
2024-09-16 8:54 ` oleksii.kurochko [this message]
2024-09-13 15:57 ` [PATCH v7 3/8] xen/riscv: set up fixmap mappings Oleksii Kurochko
2024-09-16 6:32 ` Jan Beulich
2024-09-16 9:50 ` oleksii.kurochko
2024-09-13 15:57 ` [PATCH v7 4/8] xen/riscv: introduce asm/pmap.h header Oleksii Kurochko
2024-09-13 15:57 ` [PATCH v7 5/8] xen/riscv: introduce functionality to work with CPU info Oleksii Kurochko
2024-09-16 6:48 ` Jan Beulich
2024-09-16 10:07 ` oleksii.kurochko
2024-09-13 15:57 ` [PATCH v7 6/8] xen/riscv: introduce and initialize SBI RFENCE extension Oleksii Kurochko
2024-09-13 15:57 ` [PATCH v7 7/8] xen/riscv: page table handling Oleksii Kurochko
2024-09-24 10:49 ` Jan Beulich
2024-09-24 11:30 ` oleksii.kurochko
2024-09-24 13:31 ` Jan Beulich
2024-09-25 10:07 ` oleksii.kurochko
2024-09-25 14:22 ` Jan Beulich
2024-09-25 14:50 ` oleksii.kurochko
2024-09-25 14:58 ` Jan Beulich
2024-09-27 8:49 ` oleksii.kurochko
2024-09-27 9:15 ` Jan Beulich
2024-09-27 11:32 ` oleksii.kurochko
2024-09-27 12:00 ` Jan Beulich
2024-09-13 15:57 ` [PATCH v7 8/8] xen/riscv: introduce early_fdt_map() Oleksii Kurochko
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=8a2ca782f0b059f58107a9545a63cce59a118a41.camel@gmail.com \
--to=oleksii.kurochko@gmail.com \
--cc=alistair.francis@wdc.com \
--cc=andrew.cooper3@citrix.com \
--cc=bobbyeshleman@gmail.com \
--cc=connojdavis@gmail.com \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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.