From: Wen Yao <haiwenyao@uniontech.com>
To: paul.walmsley@sifive.com, palmer@dabbelt.com,
aou@eecs.berkeley.edu, dennis@kernel.org, tj@kernel.org,
cl@linux.com
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, Wen Yao <haiwenyao@uniontech.com>
Subject: [PATCH 2/2] riscv:kconfig:select HAVE_CMPXCHG_LOCAL
Date: Wed, 26 Oct 2022 18:40:15 +0800 [thread overview]
Message-ID: <20221026104015.565468-3-haiwenyao@uniontech.com> (raw)
In-Reply-To: <20221026104015.565468-1-haiwenyao@uniontech.com>
We implement an optimised this_cpu_cmpxchg API,so select HAVE_CMPXCHG_LOCA
to open cmpxchg-local feature.
Signed-off-by: Wen Yao <haiwenyao@uniontech.com>
---
arch/riscv/Kconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
index 6b48a3ae9843..8e19df5a8227 100644
--- a/arch/riscv/Kconfig
+++ b/arch/riscv/Kconfig
@@ -88,6 +88,7 @@ config RISCV
select HAVE_ARCH_THREAD_STRUCT_WHITELIST
select HAVE_ARCH_VMAP_STACK if MMU && 64BIT
select HAVE_ASM_MODVERSIONS
+ select HAVE_CMPXCHG_LOCAL
select HAVE_CONTEXT_TRACKING_USER
select HAVE_DEBUG_KMEMLEAK
select HAVE_DMA_CONTIGUOUS if MMU
--
2.25.1
prev parent reply other threads:[~2022-10-26 10:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 10:40 [PATCH 0/2] riscv: Rewrite percpu operations and support cmpxchg-local feature Wen Yao
2022-10-26 10:40 ` [PATCH 1/2] riscv: percpu:Add riscv percpu operations Wen Yao
2022-10-26 18:54 ` Conor Dooley
2022-10-27 0:14 ` kernel test robot
2022-10-27 1:05 ` kernel test robot
2022-10-30 13:19 ` Christoph Lameter
2022-10-26 10:40 ` Wen Yao [this message]
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=20221026104015.565468-3-haiwenyao@uniontech.com \
--to=haiwenyao@uniontech.com \
--cc=aou@eecs.berkeley.edu \
--cc=cl@linux.com \
--cc=dennis@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=tj@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