mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "wuqiang.matt" <wuqiang.matt@bytedance.com>
To: Max Filippov <jcmvbkbc@gmail.com>
Cc: chris@zankel.net, andi.shyti@linux.intel.com,
	andrzej.hajda@intel.com, palmer@rivosinc.com,
	geert@linux-m68k.org, linux-kernel@vger.kernel.org,
	mattwu@163.com
Subject: Re: [PATCH v1] locking/atomic: xtensa: define arch_cmpxchg_local as __cmpxchg_local
Date: Sat, 4 Nov 2023 18:34:20 +0800	[thread overview]
Message-ID: <8e83e099-c689-410a-b889-7d8a299bf4e5@bytedance.com> (raw)
In-Reply-To: <CAMo8BfK4zDfdh9-WLq+gg1B47ht5hxhvH_j5veEj6JG38meTuw@mail.gmail.com>

On 2023/11/4 17:31, Max Filippov wrote:
> On Sat, Nov 4, 2023 at 2:06 AM wuqiang.matt <wuqiang.matt@bytedance.com> wrote:
>>
>> The xtensa architecture already has __cmpxchg_local defined upon the
>> native __cmpxchg_u32 and __generic_cmpxchg_local
> 
> This description does not make clear why this change is needed. Could you
> please expand it to cover the 'why' part?

The purpose of __cmpxchg_local() should be for arch_cmpxchg_local(), similarly
for other architectures like x86/arm/powerpc.

I noticed that arc/hexagon/openrisc/sh don't have arch_cmpxchg_local defined
because my patch triggered an error in kernel building. Then found xtensa's
definition of arch_cmpxchg_local() is not reasonable, so proposed this patch
to improve.

This change is not a must, but an improvement to simply make the codes of
arch_cmpxchg_local() more reasonable.

The patch link that introduced try_cmpxchg_local and triggered building error:
https://lore.kernel.org/all/20231023112452.6290-1-wuqiang.matt@bytedance.com/

>> Signed-off-by: wuqiang.matt <wuqiang.matt@bytedance.com>
>> ---
>>   arch/xtensa/include/asm/cmpxchg.h | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/arch/xtensa/include/asm/cmpxchg.h b/arch/xtensa/include/asm/cmpxchg.h
>> index 675a11ea8de7..956c9925df1c 100644
>> --- a/arch/xtensa/include/asm/cmpxchg.h
>> +++ b/arch/xtensa/include/asm/cmpxchg.h
>> @@ -108,7 +108,7 @@ static inline unsigned long __cmpxchg_local(volatile void *ptr,
>>    * them available.
>>    */
>>   #define arch_cmpxchg_local(ptr, o, n)                                         \
>> -       ((__typeof__(*(ptr)))__generic_cmpxchg_local((ptr), (unsigned long)(o),\
>> +       ((__typeof__(*(ptr)))__cmpxchg_local((ptr), (unsigned long)(o),        \
>>                          (unsigned long)(n), sizeof(*(ptr))))
>>   #define arch_cmpxchg64_local(ptr, o, n) __generic_cmpxchg64_local((ptr), (o), (n))
>>   #define arch_cmpxchg64(ptr, o, n)    arch_cmpxchg64_local((ptr), (o), (n))
>> --
>> 2.40.1
>>
> 
> 


  reply	other threads:[~2023-11-04 10:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-04  9:06 wuqiang.matt
2023-11-04  9:31 ` Max Filippov
2023-11-04 10:34   ` wuqiang.matt [this message]
2023-11-04 10:58   ` [PATCH v2] " wuqiang.matt

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=8e83e099-c689-410a-b889-7d8a299bf4e5@bytedance.com \
    --to=wuqiang.matt@bytedance.com \
    --cc=andi.shyti@linux.intel.com \
    --cc=andrzej.hajda@intel.com \
    --cc=chris@zankel.net \
    --cc=geert@linux-m68k.org \
    --cc=jcmvbkbc@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mattwu@163.com \
    --cc=palmer@rivosinc.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®