From: Mark Brown <broonie@kernel.org>
To: Robin Murphy <robin.murphy@arm.com>
Cc: will@kernel.org, catalin.marinas@arm.com, joro@8bytes.org,
jean-philippe@linaro.org, iommu@lists.linux.dev,
linux-arm-kernel@lists.infradead.org, mark.rutland@arm.com,
joey.gouly@arm.com, ryan.roberts@arm.com
Subject: Re: [PATCH 2/2] arm64: cpufeature: Add GCS to cpucap_is_possible()
Date: Thu, 5 Dec 2024 15:04:11 +0000 [thread overview]
Message-ID: <051c017c-a60f-48a7-b09f-07f0f32e48e3@sirena.org.uk> (raw)
In-Reply-To: <416c7369fcdce4ebb2a8f12daae234507be27e38.1733406275.git.robin.murphy@arm.com>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
On Thu, Dec 05, 2024 at 01:48:10PM +0000, Robin Murphy wrote:
> Since system_supports_gcs() ends up referring to cpucap_is_possible(),
> teach the latter about GCS for consistency with similar features.
Not clear why this is part of a series, there's no obvious relationship
with patch 1?
> static inline bool system_supports_gcs(void)
> {
> - return IS_ENABLED(CONFIG_ARM64_GCS) &&
> - alternative_has_cap_unlikely(ARM64_HAS_GCS);
> + return alternative_has_cap_unlikely(ARM64_HAS_GCS);
> }
Ah, this is bitrot since the series was on the list for so long. As
well as HAFT which Rutland mentioned it looks like _bti_kernel(),
_irq_prio_masking() and possibly others have the same thing. Ideally
we'd have no uses of IS_ENABLED() in these functions so it's a bit more
obvious. In any case
Reviewed-by: Mark Brown <broonie@kernel.org>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2024-12-05 15:11 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-05 13:48 [PATCH 1/2] iommu/arm-smmu-v3: Document SVA interaction with new pagetable features Robin Murphy
2024-12-05 13:48 ` [PATCH 2/2] arm64: cpufeature: Add GCS to cpucap_is_possible() Robin Murphy
2024-12-05 14:23 ` Mark Rutland
2024-12-05 15:04 ` Mark Brown [this message]
2024-12-05 15:25 ` Catalin Marinas
2024-12-05 15:55 ` Robin Murphy
2024-12-05 15:40 ` Mark Rutland
2024-12-05 15:52 ` Mark Brown
2024-12-05 18:14 ` [PATCH 1/2] iommu/arm-smmu-v3: Document SVA interaction with new pagetable features Jean-Philippe Brucker
2024-12-06 12:03 ` Robin Murphy
2024-12-05 18:23 ` (subset) " Catalin Marinas
2024-12-10 0:17 ` Will Deacon
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=051c017c-a60f-48a7-b09f-07f0f32e48e3@sirena.org.uk \
--to=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=iommu@lists.linux.dev \
--cc=jean-philippe@linaro.org \
--cc=joey.gouly@arm.com \
--cc=joro@8bytes.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=robin.murphy@arm.com \
--cc=ryan.roberts@arm.com \
--cc=will@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