public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Marc Zyngier <maz@kernel.org>
To: Manoj Ekbote <mekbote@qti.qualcomm.com>
Cc: "linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: FEAT_CMOW
Date: Thu, 19 Feb 2026 08:52:36 +0000	[thread overview]
Message-ID: <86y0kp9ktn.wl-maz@kernel.org> (raw)
In-Reply-To: <BL0PR02MB654847527978D284F651C7BD8D6BA@BL0PR02MB6548.namprd02.prod.outlook.com>

On Thu, 19 Feb 2026 05:21:02 +0000,
Manoj Ekbote <mekbote@qti.qualcomm.com> wrote:
> 
> Hi,
> 
> While looking at the mainline v6.18.6 sources, I noticed that
> FEAT_CMOW does not appear in the arm64 CPU capability table
> (arch/arm64/kernel/cpufeature.c). Since CMOW is a mandatory
> architectural feature starting in Arm v8.8, I expected to see it in
> the cpufeature framework.  How is the cpu feature list typically
> updated for architectural extensions like this?

When we have a use for it. FEAT_CMOW has the potential to break the
ABI we already expose to userspace, so I don't immediately see why
we'd care about it.

> Is it done only when the kernel needs to make use of the feature, or
> is there a process to actively add all mandatory architecture
> features?

The Linux kernel is thankfully not a validation tool for the
architecture, and is not aligned to any particular version of the
architecture either. A "mandatory" feature is only a requirement for
implementations, not for SW.

Thanks,

	M.

-- 
Without deviation from the norm, progress is not possible.


      reply	other threads:[~2026-02-19  8:52 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-19  5:21 FEAT_CMOW Manoj Ekbote
2026-02-19  8:52 ` Marc Zyngier [this message]

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=86y0kp9ktn.wl-maz@kernel.org \
    --to=maz@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=mekbote@qti.qualcomm.com \
    /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