mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yeoreum Yun <yeoreum.yun@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: catalin.marinas@arm.com, will@kernel.org, maz@kernel.org,
	oliver.upton@linux.dev, ardb@kernel.org, frederic@kernel.org,
	james.morse@arm.com, joey.gouly@arm.com,
	scott@os.amperecomputing.com,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/6] arm64/Kconfig: add LSUI Kconfig
Date: Wed, 11 Jun 2025 15:48:23 +0100	[thread overview]
Message-ID: <aEmXNw01W6IosBXt@e129823.arm.com> (raw)
In-Reply-To: <07190b99-5e8c-4de0-b460-248ec39996f4@sirena.org.uk>

Hi Mark,

> On Wed, Jun 11, 2025 at 11:49:12AM +0100, Yeoreum Yun wrote:
>
> > +menu "v9.6 architectural features"
> > +
> > +config AS_HAS_LSUI
> > +	def_bool $(as-instr,.arch_extension lsui)
> > +
> > +endmenu # "v9.6 architectural features"
> > +
>
> This is adding a menu with no user selectable options, does that not
> result in a confusing user experience?We do often add toolchain
> feature checks inside the menus but that's usually associated with
> hiding a user selectable option, if there isn't one (or any other option
> for that arch version yet) we should probably put the check elsewhere.

Well even the v9.4 menu can be printed a menu with no user selcatable
optoins when UPROBE is enabled (ARM64_GCS depend on !UPROBE).
But without any selectable options adding the menu seems weird as you said.

Like AS_HAS_MOPS, let me define AS_HAS_LSUI without menu.
I'll remove the menu entry.

Thanks.

--
Sincerely,
Yeoreum Yun

  reply	other threads:[~2025-06-11 14:49 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-11 10:49 [PATCH 0/6] support FEAT_LSUI and apply it on futex atomic ops Yeoreum Yun
2025-06-11 10:49 ` [PATCH 1/6] arm64: cpufeature: add FEAT_LSUI Yeoreum Yun
2025-06-11 13:29   ` Mark Brown
2025-06-11 14:52     ` Yeoreum Yun
2025-06-11 15:16   ` Marc Zyngier
2025-06-11 17:55     ` Yeoreum Yun
2025-06-11 10:49 ` [PATCH 2/6] arm64/Kconfig: add LSUI Kconfig Yeoreum Yun
2025-06-11 13:34   ` Mark Brown
2025-06-11 14:48     ` Yeoreum Yun [this message]
2025-06-11 15:17   ` Marc Zyngier
2025-06-11 17:54     ` Yeoreum Yun
2025-06-12  6:33       ` Marc Zyngier
2025-06-11 10:49 ` [PATCH 3/6] arm64/futex: move futex atomic logic with clearing PAN bit Yeoreum Yun
2025-06-11 10:49 ` [PATCH 4/6] arm64/futex: add futex atomic operation with FEAT_LSUI Yeoreum Yun
2025-06-11 10:49 ` [PATCH 5/6] arm64/asm: introduce lsui.h Yeoreum Yun
2025-06-11 10:49 ` [PATCH 6/6] arm64/futex: support futex with FEAT_LSUI Yeoreum Yun

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=aEmXNw01W6IosBXt@e129823.arm.com \
    --to=yeoreum.yun@arm.com \
    --cc=ardb@kernel.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=frederic@kernel.org \
    --cc=james.morse@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=scott@os.amperecomputing.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
all inboxes | Powered by JetHome®