From: "wuqiang.matt" <wuqiang.matt@bytedance.com>
To: vgupta@kernel.org, bcain@quicinc.com, jonas@southpole.se,
stefan.kristiansson@saunalahti.fi, shorne@gmail.com,
geert@linux-m68k.org, andi.shyti@linux.intel.com,
mingo@kernel.org, palmer@rivosinc.com, andrzej.hajda@intel.com,
arnd@arndb.de, peterz@infradead.orgm, mhiramat@kernel.org
Cc: linux-snps-arc@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-hexagon@vger.kernel.org, linux-openrisc@vger.kernel.org,
linux-trace-kernel@vger.kernel.org, mattwu@163.com,
linux@roeck-us.ne, "wuqiang.matt" <wuqiang.matt@bytedance.com>
Subject: [PATCH v2 0/4] locking/atomic: arch_cmpxchg[64]_local undefined
Date: Sat, 4 Nov 2023 17:16:11 +0800 [thread overview]
Message-ID: <20231104091615.4884-1-wuqiang.matt@bytedance.com> (raw)
This patch series implement arch_cmpxchg[64]_local for arc,
openrisc and hexagon.
For architectures that support native cmpxchg, we'd like to
implement arch_cmpxchg[64]_local with the native variants of
supported data size. If not, the generci_cmpxchg[64]_local
will be used.
wuqiang.matt (4):
locking/atomic: arc: data size checking in arch_cmpxchg
locking/atomic: arc: arch_cmpxchg[64]_local undefined
locking/atomic: openrisc: arch_cmpxchg[64]_local undefined
locking/atomic: hexagon: arch_cmpxchg[64]_local undefined
arch/arc/include/asm/cmpxchg.h | 40 ++++++++++++++++++----
arch/hexagon/include/asm/cmpxchg.h | 51 ++++++++++++++++++++++++++++-
arch/openrisc/include/asm/cmpxchg.h | 6 ++++
3 files changed, 90 insertions(+), 7 deletions(-)
--
2.40.1
next reply other threads:[~2023-11-04 9:16 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-04 9:16 wuqiang.matt [this message]
2023-11-04 9:16 ` [PATCH v2 1/4] locking/atomic: arc: data size checking in arch_cmpxchg wuqiang.matt
2023-11-08 1:02 ` Masami Hiramatsu
2023-11-04 9:16 ` [PATCH v2 2/4] locking/atomic: arc: arch_cmpxchg[64]_local undefined wuqiang.matt
2023-11-08 1:02 ` Masami Hiramatsu
2023-11-04 9:16 ` [PATCH v2 3/4] locking/atomic: openrisc: " wuqiang.matt
2023-11-08 1:03 ` Masami Hiramatsu
2023-11-04 9:16 ` [PATCH v2 4/4] locking/atomic: hexagon: " wuqiang.matt
2023-11-08 1:04 ` Masami Hiramatsu
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=20231104091615.4884-1-wuqiang.matt@bytedance.com \
--to=wuqiang.matt@bytedance.com \
--cc=andi.shyti@linux.intel.com \
--cc=andrzej.hajda@intel.com \
--cc=arnd@arndb.de \
--cc=bcain@quicinc.com \
--cc=geert@linux-m68k.org \
--cc=jonas@southpole.se \
--cc=linux-hexagon@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-openrisc@vger.kernel.org \
--cc=linux-snps-arc@lists.infradead.org \
--cc=linux-trace-kernel@vger.kernel.org \
--cc=linux@roeck-us.ne \
--cc=mattwu@163.com \
--cc=mhiramat@kernel.org \
--cc=mingo@kernel.org \
--cc=palmer@rivosinc.com \
--cc=peterz@infradead.orgm \
--cc=shorne@gmail.com \
--cc=stefan.kristiansson@saunalahti.fi \
--cc=vgupta@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).