All of lore.kernel.org
 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, joey.gouly@arm.com, james.morse@arm.com,
	ardb@kernel.org, scott@os.amperecomputing.com,
	suzuki.poulose@arm.com, yuzenghui@huawei.com,
	mark.rutland@arm.com, linux-arm-kernel@lists.infradead.org,
	kvmarm@lists.linux.dev, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 2/5] KVM: arm64: expose FEAT_LSUI to guest
Date: Mon, 22 Sep 2025 15:49:37 +0100	[thread overview]
Message-ID: <aNFiAZVT+XDCBX4r@e129823.arm.com> (raw)
In-Reply-To: <aNEkNF8rvb_e9DKd@finisterre.sirena.org.uk>

Hi Mark,

[...]
> >  	case SYS_ID_AA64ISAR3_EL1:
> > -		val &= ID_AA64ISAR3_EL1_FPRCVT | ID_AA64ISAR3_EL1_FAMINMAX;
> > +		val &= ID_AA64ISAR3_EL1_FPRCVT | ID_AA64ISAR3_EL1_FAMINMAX |
> > +		       ID_AA64ISAR3_EL1_LSUI;
>
> This should be added to set_id_regs, but ID_AA64ISAR3_EL1 isn't covered
> by that yet.  I posted a series for that the other day:
>
>    https://lore.kernel.org/r/20250920-kvm-arm64-id-aa64isar3-el1-v1-0-1764c1c1c96d@kernel.org

Thank to let me know missing to add kselftest feature for this.
I'll add it :)


--
Sincerely,
Yeoreum Yun

  reply	other threads:[~2025-09-22 14:50 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-22 10:22 [PATCH v9 0/6] support FEAT_LSUI and apply it on futex atomic ops Yeoreum Yun
2025-09-22 10:22 ` [PATCH v9 1/5] arm64: cpufeature: add FEAT_LSUI Yeoreum Yun
2025-09-22 10:22 ` [PATCH v9 2/5] KVM: arm64: expose FEAT_LSUI to guest Yeoreum Yun
2025-09-22 10:25   ` Mark Brown
2025-09-22 14:49     ` Yeoreum Yun [this message]
2025-09-23  9:28       ` Yeoreum Yun
2025-09-22 10:22 ` [PATCH v9 3/5] arm64: Kconfig: Detect toolchain support for LSUI Yeoreum Yun
2025-09-22 10:22 ` [PATCH v9 4/5] arm64: futex: refactor futex atomic operation Yeoreum Yun
2025-09-22 10:22 ` [PATCH v9 5/5] 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=aNFiAZVT+XDCBX4r@e129823.arm.com \
    --to=yeoreum.yun@arm.com \
    --cc=ardb@kernel.org \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=james.morse@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mark.rutland@arm.com \
    --cc=maz@kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=scott@os.amperecomputing.com \
    --cc=suzuki.poulose@arm.com \
    --cc=will@kernel.org \
    --cc=yuzenghui@huawei.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 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.