From: Marc Zyngier <maz@kernel.org>
To: Yeoreum Yun <yeoreum.yun@arm.com>
Cc: catalin.marinas@arm.com, will@kernel.org, broonie@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 v3 2/7] arm64/kvm: expose FEAT_LSUI to guest
Date: Wed, 02 Jul 2025 18:17:34 +0100 [thread overview]
Message-ID: <86cyaibjgx.wl-maz@kernel.org> (raw)
In-Reply-To: <20250617183635.1266015-3-yeoreum.yun@arm.com>
On Tue, 17 Jun 2025 19:36:30 +0100,
Yeoreum Yun <yeoreum.yun@arm.com> wrote:
>
> expose FEAT_LSUI to guest.
>
> Signed-off-by: Yeoreum Yun <yeoreum.yun@arm.com>
> ---
> arch/arm64/kvm/sys_regs.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/kvm/sys_regs.c b/arch/arm64/kvm/sys_regs.c
> index 76c2f0da821f..5c5a9c3ace2f 100644
> --- a/arch/arm64/kvm/sys_regs.c
> +++ b/arch/arm64/kvm/sys_regs.c
> @@ -1636,7 +1636,8 @@ static u64 __kvm_read_sanitised_id_reg(const struct kvm_vcpu *vcpu,
> val &= ~ARM64_FEATURE_MASK(ID_AA64ISAR2_EL1_WFxT);
> break;
> 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;
> break;
> case SYS_ID_AA64MMFR2_EL1:
> val &= ~ID_AA64MMFR2_EL1_CCIDX_MASK;
> @@ -2921,7 +2922,7 @@ static const struct sys_reg_desc sys_reg_descs[] = {
> ID_AA64ISAR2_EL1_APA3 |
> ID_AA64ISAR2_EL1_GPA3)),
> ID_WRITABLE(ID_AA64ISAR3_EL1, (ID_AA64ISAR3_EL1_FPRCVT |
> - ID_AA64ISAR3_EL1_FAMINMAX)),
> + ID_AA64ISAR3_EL1_FAMINMAX | ID_AA64ISAR3_EL1_LSUI)),
> ID_UNALLOCATED(6,4),
> ID_UNALLOCATED(6,5),
> ID_UNALLOCATED(6,6),
In the future, please Cc the relevant people and mailing lists.
With $SUBJECT fixed to match the KVM/arm64 log,
Acked-by: Marc Zyngier <maz@kernel.org>
M.
--
Without deviation from the norm, progress is not possible.
next prev parent reply other threads:[~2025-07-02 17:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-17 18:36 [PATCH v3 0/7] support FEAT_LSUI and apply it on futex atomic ops Yeoreum Yun
2025-06-17 18:36 ` [PATCH v3 1/7] arm64: cpufeature: add FEAT_LSUI Yeoreum Yun
2025-06-17 18:36 ` [PATCH v3 2/7] arm64/kvm: expose FEAT_LSUI to guest Yeoreum Yun
2025-07-02 17:17 ` Marc Zyngier [this message]
2025-06-17 18:36 ` [PATCH v3 3/7] arm64/Kconfig: add LSUI Kconfig Yeoreum Yun
2025-06-17 18:36 ` [PATCH v3 4/7] arm64/futex: move futex atomic logic with clearing PAN bit Yeoreum Yun
2025-06-17 18:36 ` [PATCH v3 5/7] arm64/futex: add futex atomic operation with FEAT_LSUI Yeoreum Yun
2025-06-17 18:36 ` [PATCH v3 6/7] arm64/asm: introduce lsui.h Yeoreum Yun
2025-06-17 18:36 ` [PATCH v3 7/7] arm64/futex: support futex with FEAT_LSUI Yeoreum Yun
2025-06-26 7:56 ` [PATCH v3 0/7] support FEAT_LSUI and apply it on futex atomic ops 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=86cyaibjgx.wl-maz@kernel.org \
--to=maz@kernel.org \
--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=oliver.upton@linux.dev \
--cc=scott@os.amperecomputing.com \
--cc=will@kernel.org \
--cc=yeoreum.yun@arm.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;
as well as URLs for NNTP newsgroup(s).