From: Robin Murphy <robin.murphy@arm.com>
To: Catalin Marinas <catalin.marinas@arm.com>,
Mark Brown <broonie@kernel.org>
Cc: will@kernel.org, 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:55:11 +0000 [thread overview]
Message-ID: <6129a590-6b1b-4368-8bcc-a09a8754bbe5@arm.com> (raw)
In-Reply-To: <Z1HF3i-mAAXDHKUP@arm.com>
On 05/12/2024 3:25 pm, Catalin Marinas wrote:
> On Thu, Dec 05, 2024 at 03:04:11PM +0000, Mark Brown wrote:
>> 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?
>
> No, probably Robing forgot to pass --no-thread to git.
Yeah, this was just a tangent from poking around figuring out how to
detect GCS being enabled for the main patch.
>>> 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>
>
> Thanks. This patch will go in via the arm64 tree. I'll leave the other
> for the smmu tree.
Thanks!
Robin.
next prev parent reply other threads:[~2024-12-05 15:56 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
2024-12-05 15:25 ` Catalin Marinas
2024-12-05 15:55 ` Robin Murphy [this message]
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=6129a590-6b1b-4368-8bcc-a09a8754bbe5@arm.com \
--to=robin.murphy@arm.com \
--cc=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=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