From: Will Deacon <will@kernel.org>
To: Joey Gouly <joey.gouly@arm.com>
Cc: linux-arm-kernel@lists.infradead.org, catalin.marinas@arm.com
Subject: Re: [PATCH v1] arm64: cpufeature: add POE to cpucap_is_possible()
Date: Mon, 14 Oct 2024 18:13:38 +0100 [thread overview]
Message-ID: <20241014171337.GA18341@willie-the-truck> (raw)
In-Reply-To: <20241008140121.2774348-1-joey.gouly@arm.com>
On Tue, Oct 08, 2024 at 03:01:21PM +0100, Joey Gouly wrote:
> Since de66cb37ab6 ("arm64: Add cpucap_is_possible()"),
> alternative_has_cap_unlikely() includes the IS_ENABLED() check.
>
> Add CONFIG_ARM64_POE to cpucap_is_possible() to avoid the explicit check.
>
> Signed-off-by: Joey Gouly <joey.gouly@arm.com>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: Will Deacon <will@kernel.org>
> ---
>
> Small cosmetic change I noticed when looking at some other patches.
>
> arch/arm64/include/asm/cpucaps.h | 2 ++
> arch/arm64/include/asm/cpufeature.h | 3 +--
> 2 files changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/include/asm/cpucaps.h b/arch/arm64/include/asm/cpucaps.h
> index a6e5b07b64fd..a08a1212ffbb 100644
> --- a/arch/arm64/include/asm/cpucaps.h
> +++ b/arch/arm64/include/asm/cpucaps.h
> @@ -42,6 +42,8 @@ cpucap_is_possible(const unsigned int cap)
> return IS_ENABLED(CONFIG_ARM64_BTI);
> case ARM64_HAS_TLB_RANGE:
> return IS_ENABLED(CONFIG_ARM64_TLB_RANGE);
> + case ARM64_HAS_S1POE:
> + return IS_ENABLED(CONFIG_ARM64_POE);
> case ARM64_UNMAP_KERNEL_AT_EL0:
> return IS_ENABLED(CONFIG_UNMAP_KERNEL_AT_EL0);
> case ARM64_WORKAROUND_843419:
> diff --git a/arch/arm64/include/asm/cpufeature.h b/arch/arm64/include/asm/cpufeature.h
> index 3d261cc123c1..4b6bc0bac9b9 100644
> --- a/arch/arm64/include/asm/cpufeature.h
> +++ b/arch/arm64/include/asm/cpufeature.h
> @@ -834,8 +834,7 @@ static inline bool system_supports_lpa2(void)
>
> static inline bool system_supports_poe(void)
> {
> - return IS_ENABLED(CONFIG_ARM64_POE) &&
> - alternative_has_cap_unlikely(ARM64_HAS_S1POE);
> + return alternative_has_cap_unlikely(ARM64_HAS_S1POE);
> }
>
> int do_emulate_mrs(struct pt_regs *regs, u32 sys_reg, u32 rt);
> --
> 2.25.1
Acked-by: Will Deacon <will@kernel.org>
Will
next prev parent reply other threads:[~2024-10-14 17:17 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-08 14:01 [PATCH v1] arm64: cpufeature: add POE to cpucap_is_possible() Joey Gouly
2024-10-14 17:13 ` Will Deacon [this message]
2024-10-16 16:30 ` Catalin Marinas
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=20241014171337.GA18341@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=joey.gouly@arm.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox