From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: [Suggestion] ARM64: kernel: compiling issue, need implement cmpxchg64 with assembler language.
Date: Sat, 20 Apr 2013 09:32:02 +0200 [thread overview]
Message-ID: <2182812.ymprEm6XBb@wuerfel> (raw)
In-Reply-To: <5171FD67.2080104@asianux.com>
On Saturday 20 April 2013 10:28:55 Chen Gang wrote:
>
> -------------------------------patch begin--------------------------------------
>
> diff --git a/arch/arm64/include/asm/cmpxchg.h b/arch/arm64/include/asm/cmpxchg.h
> index 968b5cb..b572d2b 100644
> --- a/arch/arm64/include/asm/cmpxchg.h
> +++ b/arch/arm64/include/asm/cmpxchg.h
> @@ -170,4 +170,6 @@ static inline unsigned long __cmpxchg_mb(volatile void *ptr, unsigned long old,
> (unsigned long)(n), \
> sizeof(*(ptr))))
>
> +#define cmpxchg64(ptr,o,n) cmpxchg((ptr),(o),(n))
> +
> #endif /* __ASM_CMPXCHG_H */
Yes, this looks good. Please provide the same for cmpxchg64_local.
> -------------------------------patch end----------------------------------------
>
>
>
> I think, we can also reference the implementation of s390:
> it is in arch/s390/include/asm/cmpxchg.h.
> since we are ARM64, excluding ARM(32,16...), we can only consider 64-bit.
> if in the future, ARM64 and ARM are merged together:
> we can use CONFIG_64BIT to switch the cmpxchg64 definition.
> if define CONFIG_64BIT, use cmpxchg instead of cmpxchg64.
> else, use the definition of ARM (arch/arm/include/asm/cmpxchg.h already defines cmpxchg64)
I would not worry aobut merging the two at the moment.
> -------------------------------reference begin----------------------------------
>
> #ifdef CONFIG_64BIT
> #define cmpxchg64(ptr, o, n) \
> ({ \
> cmpxchg((ptr), (o), (n)); \
> })
> #else /* CONFIG_64BIT */
> ...
> -------------------------------reference end------------------------------------
This implementation in unnecessarily verbose, I think the one you have
above is nicer.
Arnd
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de>
To: Chen Gang <gang.chen@asianux.com>
Cc: Catalin Marinas <Catalin.Marinas@arm.com>,
Will Deacon <will.deacon@arm.com>,
Tony Lindgren <tony@atomide.com>,
"olof@lixom.net" <olof@lixom.net>,
Santosh Shilimkar <santosh.shilimkar@ti.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [Suggestion] ARM64: kernel: compiling issue, need implement cmpxchg64 with assembler language.
Date: Sat, 20 Apr 2013 09:32:02 +0200 [thread overview]
Message-ID: <2182812.ymprEm6XBb@wuerfel> (raw)
In-Reply-To: <5171FD67.2080104@asianux.com>
On Saturday 20 April 2013 10:28:55 Chen Gang wrote:
>
> -------------------------------patch begin--------------------------------------
>
> diff --git a/arch/arm64/include/asm/cmpxchg.h b/arch/arm64/include/asm/cmpxchg.h
> index 968b5cb..b572d2b 100644
> --- a/arch/arm64/include/asm/cmpxchg.h
> +++ b/arch/arm64/include/asm/cmpxchg.h
> @@ -170,4 +170,6 @@ static inline unsigned long __cmpxchg_mb(volatile void *ptr, unsigned long old,
> (unsigned long)(n), \
> sizeof(*(ptr))))
>
> +#define cmpxchg64(ptr,o,n) cmpxchg((ptr),(o),(n))
> +
> #endif /* __ASM_CMPXCHG_H */
Yes, this looks good. Please provide the same for cmpxchg64_local.
> -------------------------------patch end----------------------------------------
>
>
>
> I think, we can also reference the implementation of s390:
> it is in arch/s390/include/asm/cmpxchg.h.
> since we are ARM64, excluding ARM(32,16...), we can only consider 64-bit.
> if in the future, ARM64 and ARM are merged together:
> we can use CONFIG_64BIT to switch the cmpxchg64 definition.
> if define CONFIG_64BIT, use cmpxchg instead of cmpxchg64.
> else, use the definition of ARM (arch/arm/include/asm/cmpxchg.h already defines cmpxchg64)
I would not worry aobut merging the two at the moment.
> -------------------------------reference begin----------------------------------
>
> #ifdef CONFIG_64BIT
> #define cmpxchg64(ptr, o, n) \
> ({ \
> cmpxchg((ptr), (o), (n)); \
> })
> #else /* CONFIG_64BIT */
> ...
> -------------------------------reference end------------------------------------
This implementation in unnecessarily verbose, I think the one you have
above is nicer.
Arnd
next prev parent reply other threads:[~2013-04-20 7:32 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-19 11:45 [Suggestion] ARM64: kernel: compiling issue, need implement cmpxchg64 with assembler language Chen Gang
2013-04-19 11:45 ` Chen Gang
2013-04-19 12:12 ` Arnd Bergmann
2013-04-19 12:12 ` Arnd Bergmann
2013-04-20 2:28 ` Chen Gang
2013-04-20 2:28 ` Chen Gang
2013-04-20 7:32 ` Arnd Bergmann [this message]
2013-04-20 7:32 ` Arnd Bergmann
2013-04-22 5:08 ` Chen Gang
2013-04-22 5:08 ` Chen Gang
2013-04-22 5:08 ` [PATCH] ARM64: kernel: compiling issue, define cmpxchg64 and cmpxchg64_local for outside using Chen Gang
2013-04-22 5:08 ` Chen Gang
2013-04-23 10:48 ` Catalin Marinas
2013-04-23 10:48 ` Catalin Marinas
2013-04-23 10:54 ` Chen Gang
2013-04-23 10:54 ` Chen Gang
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=2182812.ymprEm6XBb@wuerfel \
--to=arnd@arndb.de \
--cc=linux-arm-kernel@lists.infradead.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.