From: Christophe Leroy <christophe.leroy@csgroup.eu>
To: Kautuk Consul <kconsul@linux.vnet.ibm.com>
Cc: Michael Ellerman <mpe@ellerman.id.au>,
Nicholas Piggin <npiggin@gmail.com>,
Rohan McLure <rmclure@linux.ibm.com>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] arch/powerpc/include/asm/barrier.h: redefine rmb and wmb to lwsync
Date: Wed, 22 Feb 2023 09:51:22 +0000 [thread overview]
Message-ID: <2cf06ae7-b3cb-8d17-afef-df1834a84dce@csgroup.eu> (raw)
In-Reply-To: <Y/XkjobvDPFErM7J@li-a450e7cc-27df-11b2-a85c-b5a9ac31e8ef.ibm.com>
Le 22/02/2023 à 10:46, Kautuk Consul a écrit :
>>
>> Reviewed-by: Christophe Leroy <christophe.leroy@csgroup.eu>
> Thanks!
>>
>>> ---
>>> arch/powerpc/include/asm/barrier.h | 7 +++++++
>>> 1 file changed, 7 insertions(+)
>>>
>>> diff --git a/arch/powerpc/include/asm/barrier.h b/arch/powerpc/include/asm/barrier.h
>>> index b95b666f0374..e088dacc0ee8 100644
>>> --- a/arch/powerpc/include/asm/barrier.h
>>> +++ b/arch/powerpc/include/asm/barrier.h
>>> @@ -36,8 +36,15 @@
>>> * heavy-weight sync, so smp_wmb() can be a lighter-weight eieio.
>>> */
>>> #define __mb() __asm__ __volatile__ ("sync" : : : "memory")
>>> +
>>> +/* The sub-arch has lwsync. */
>>> +#if defined(CONFIG_PPC64) || defined(CONFIG_PPC_E500MC)
>>> +#define __rmb() __asm__ __volatile__ ("lwsync" : : : "memory")
>>> +#define __wmb() __asm__ __volatile__ ("lwsync" : : : "memory")
>>
>> I'd have preferred with 'asm volatile' though.
> Sorry about that! That wasn't the intent of this patch.
> Probably another patch series should change this manner of #defining
> assembly.
Why adding new line wrong then have to have another patch to make them
right ?
When you build a new house in an old village, you first build your house
with old materials and then you replace everything with new material ?
next prev parent reply other threads:[~2023-02-22 9:53 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 9:03 Kautuk Consul
2023-02-22 9:30 ` Kautuk Consul
2023-02-22 9:44 ` Christophe Leroy
2023-02-22 9:49 ` Kautuk Consul
2023-02-22 9:43 ` Christophe Leroy
2023-02-22 9:46 ` Kautuk Consul
2023-02-22 9:51 ` Christophe Leroy [this message]
2023-02-22 9:55 ` Kautuk Consul
2023-02-22 17:47 ` Paul E. McKenney
2023-02-23 3:51 ` Michael Ellerman
2023-02-23 4:07 ` Kautuk Consul
2023-02-23 4:43 ` Kautuk Consul
2023-02-23 9:24 ` Michael Ellerman
2023-02-23 4:01 ` Kautuk Consul
2023-02-23 4:16 ` Paul E. McKenney
2023-02-23 4:22 ` Kautuk Consul
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=2cf06ae7-b3cb-8d17-afef-df1834a84dce@csgroup.eu \
--to=christophe.leroy@csgroup.eu \
--cc=kconsul@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mpe@ellerman.id.au \
--cc=npiggin@gmail.com \
--cc=rmclure@linux.ibm.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
all inboxes | Powered by JetHome®