From: Marc Zyngier <maz@kernel.org>
To: Catalin Marinas <catalin.marinas@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Mark Brown <broonie@kernel.org>,
stable@vger.kernel.org
Subject: Re: [PATCH] arm64: Filter out SVE hwcaps when FEAT_SVE isn't implemented
Date: Fri, 03 Jan 2025 18:00:43 +0000 [thread overview]
Message-ID: <87ldvrrd4k.wl-maz@kernel.org> (raw)
In-Reply-To: <Z3gg23G00THN-Ev5@arm.com>
On Fri, 03 Jan 2025 17:39:39 +0000,
Catalin Marinas <catalin.marinas@arm.com> wrote:
>
> On Fri, Jan 03, 2025 at 05:20:05PM +0000, Catalin Marinas wrote:
> > On Fri, Jan 03, 2025 at 02:26:35PM +0000, Marc Zyngier wrote:
> > > @@ -3022,6 +3027,13 @@ static const struct arm64_cpu_capabilities arm64_features[] = {
> > > .matches = match, \
> > > }
> > >
> > > +#define HWCAP_CAP_MATCH_ID(match, reg, field, min_value, cap_type, cap) \
> > > + { \
> > > + __HWCAP_CAP(#cap, cap_type, cap) \
> > > + HWCAP_CPUID_MATCH(reg, field, min_value) \
> > > + .matches = match, \
> > > + }
> >
> > Do we actually need this macro?
>
> Ignore me, we still need this macro as HWCAP_CAP_MATCH does not take all
> the arguments. Maybe not the read_scoped_sysreg() change though.
Ah, I just replied to your earlier email. Agreed on avoiding the
read_scoped_sysreg() change, replacing it with system_supports_sve().
I'll respin the change now.
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-01-03 18:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-03 14:26 [PATCH] arm64: Filter out SVE hwcaps when FEAT_SVE isn't implemented Marc Zyngier
2025-01-03 17:20 ` Catalin Marinas
2025-01-03 17:39 ` Catalin Marinas
2025-01-03 18:00 ` Marc Zyngier [this message]
2025-01-03 17:58 ` Marc Zyngier
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=87ldvrrd4k.wl-maz@kernel.org \
--to=maz@kernel.org \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=stable@vger.kernel.org \
--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 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.