From: Minda Chen <minda.chen@starfivetech.com> To: Conor Dooley <conor@kernel.org>, Jisheng Zhang <jszhang@kernel.org>, Samuel Holland <samuel@sholland.org>, Dao Lu <daolu@rivosinc.com>, "Heiko Stuebner" <heiko@sntech.de>, Paul Walmsley <paul.walmsley@sifive.com>, "Palmer Dabbelt" <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu> Cc: <linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>, "Minda Chen" <minda.chen@starfivetech.com> Subject: [PATCH v1] riscv: Using TOOLCHAIN_HAS_ZIHINTPAUSE marco replace zihintpause Date: Wed, 2 Aug 2023 14:42:15 +0800 [thread overview] Message-ID: <20230802064215.31111-1-minda.chen@starfivetech.com> (raw) Actually it is a part of Conor's commit aae538cd03bc ("riscv: fix detection of toolchain Zihintpause support"). It is looks like a merge issue. Samuel's commit 0b1d60d6dd9e ("riscv: Fix build with CONFIG_CC_OPTIMIZE_FOR_SIZE=y") do not base on Conor's commit and revert to __riscv_zihintpause. So this patch can fix it. Signed-off-by: Minda Chen <minda.chen@starfivetech.com> --- arch/riscv/include/asm/vdso/processor.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/riscv/include/asm/vdso/processor.h b/arch/riscv/include/asm/vdso/processor.h index 14f5d27783b8..96b65a5396df 100644 --- a/arch/riscv/include/asm/vdso/processor.h +++ b/arch/riscv/include/asm/vdso/processor.h @@ -14,7 +14,7 @@ static inline void cpu_relax(void) __asm__ __volatile__ ("div %0, %0, zero" : "=r" (dummy)); #endif -#ifdef __riscv_zihintpause +#ifdef CONFIG_TOOLCHAIN_HAS_ZIHINTPAUSE /* * Reduce instruction retirement. * This assumes the PC changes. -- 2.17.1
WARNING: multiple messages have this Message-ID (diff)
From: Minda Chen <minda.chen@starfivetech.com> To: Conor Dooley <conor@kernel.org>, Jisheng Zhang <jszhang@kernel.org>, Samuel Holland <samuel@sholland.org>, Dao Lu <daolu@rivosinc.com>, "Heiko Stuebner" <heiko@sntech.de>, Paul Walmsley <paul.walmsley@sifive.com>, "Palmer Dabbelt" <palmer@dabbelt.com>, Albert Ou <aou@eecs.berkeley.edu> Cc: <linux-kernel@vger.kernel.org>, <linux-riscv@lists.infradead.org>, "Minda Chen" <minda.chen@starfivetech.com> Subject: [PATCH v1] riscv: Using TOOLCHAIN_HAS_ZIHINTPAUSE marco replace zihintpause Date: Wed, 2 Aug 2023 14:42:15 +0800 [thread overview] Message-ID: <20230802064215.31111-1-minda.chen@starfivetech.com> (raw) Actually it is a part of Conor's commit aae538cd03bc ("riscv: fix detection of toolchain Zihintpause support"). It is looks like a merge issue. Samuel's commit 0b1d60d6dd9e ("riscv: Fix build with CONFIG_CC_OPTIMIZE_FOR_SIZE=y") do not base on Conor's commit and revert to __riscv_zihintpause. So this patch can fix it. Signed-off-by: Minda Chen <minda.chen@starfivetech.com> --- arch/riscv/include/asm/vdso/processor.h | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/arch/riscv/include/asm/vdso/processor.h b/arch/riscv/include/asm/vdso/processor.h index 14f5d27783b8..96b65a5396df 100644 --- a/arch/riscv/include/asm/vdso/processor.h +++ b/arch/riscv/include/asm/vdso/processor.h @@ -14,7 +14,7 @@ static inline void cpu_relax(void) __asm__ __volatile__ ("div %0, %0, zero" : "=r" (dummy)); #endif -#ifdef __riscv_zihintpause +#ifdef CONFIG_TOOLCHAIN_HAS_ZIHINTPAUSE /* * Reduce instruction retirement. * This assumes the PC changes. -- 2.17.1 _______________________________________________ linux-riscv mailing list linux-riscv@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-riscv
next reply other threads:[~2023-08-02 6:43 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-02 6:42 Minda Chen [this message] 2023-08-02 6:42 ` [PATCH v1] riscv: Using TOOLCHAIN_HAS_ZIHINTPAUSE marco replace zihintpause Minda Chen 2023-08-02 6:54 ` Conor Dooley 2023-08-02 6:54 ` Conor Dooley 2023-08-02 7:32 ` Minda Chen 2023-08-02 7:32 ` Minda Chen 2023-08-02 7:48 ` Conor Dooley 2023-08-02 7:48 ` Conor Dooley 2023-08-02 8:17 ` Minda Chen 2023-08-02 8:17 ` Minda Chen 2023-08-02 8:33 ` Greg KH 2023-08-02 8:33 ` Greg KH 2023-08-02 8:52 ` Conor Dooley 2023-08-02 8:52 ` Conor Dooley 2023-08-02 9:42 ` Greg KH 2023-08-02 9:42 ` Greg KH 2023-08-02 9:50 ` Conor Dooley 2023-08-02 9:50 ` Conor Dooley
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=20230802064215.31111-1-minda.chen@starfivetech.com \ --to=minda.chen@starfivetech.com \ --cc=aou@eecs.berkeley.edu \ --cc=conor@kernel.org \ --cc=daolu@rivosinc.com \ --cc=heiko@sntech.de \ --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 \ --cc=samuel@sholland.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: linkBe 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.