From: "Clément Léger" <cleger@rivosinc.com>
To: Jisheng Zhang <jszhang@kernel.org>,
Paul Walmsley <paul.walmsley@sifive.com>,
Palmer Dabbelt <palmer@dabbelt.com>,
Albert Ou <aou@eecs.berkeley.edu>
Cc: linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] riscv: select ARCH_USE_SYM_ANNOTATIONS
Date: Mon, 8 Jul 2024 11:20:56 +0200 [thread overview]
Message-ID: <beb8a766-8143-40ad-912b-b04f7937d4a4@rivosinc.com> (raw)
In-Reply-To: <20240705132308.1469-1-jszhang@kernel.org>
On 05/07/2024 15:23, Jisheng Zhang wrote:
> After commit 76329c693924 ("riscv: Use SYM_*() assembly macros instead
> of deprecated ones"), riscv has been to the new style SYM_ assembler
> annotations. So select ARCH_USE_SYM_ANNOTATIONS to ensure the
> deprecated macros such as ENTRY(), END(), WEAK() and so on are not
> available and we don't regress.
Hi Jisheng,
On which branch/series is it based ? I tried it and it fails on
errata_cip-435.s which still contains some uses of ENTRY():
ENTRY(sifive_cip_453_page_fault_trp)
Thanks,
Clément
>
> Signed-off-by: Jisheng Zhang <jszhang@kernel.org>
> ---
> arch/riscv/Kconfig | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/arch/riscv/Kconfig b/arch/riscv/Kconfig
> index 0525ee2d63c7..c51b32a8ddff 100644
> --- a/arch/riscv/Kconfig
> +++ b/arch/riscv/Kconfig
> @@ -62,6 +62,7 @@ config RISCV
> select ARCH_USE_CMPXCHG_LOCKREF if 64BIT
> select ARCH_USE_MEMTEST
> select ARCH_USE_QUEUED_RWLOCKS
> + select ARCH_USE_SYM_ANNOTATIONS
> select ARCH_USES_CFI_TRAPS if CFI_CLANG
> select ARCH_WANT_BATCHED_UNMAP_TLB_FLUSH if MMU
> select ARCH_WANT_DEFAULT_TOPDOWN_MMAP_LAYOUT if MMU
next prev parent reply other threads:[~2024-07-08 9:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-05 13:23 Jisheng Zhang
2024-07-08 9:20 ` Clément Léger [this message]
2024-07-08 11:26 ` Jisheng Zhang
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=beb8a766-8143-40ad-912b-b04f7937d4a4@rivosinc.com \
--to=cleger@rivosinc.com \
--cc=aou@eecs.berkeley.edu \
--cc=jszhang@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.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®