linux-doc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ben Horgan <ben.horgan@arm.com>
To: Mark Brown <broonie@kernel.org>,
	Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>, Jonathan Corbet <corbet@lwn.net>,
	Marc Zyngier <maz@kernel.org>,
	Oliver Upton <oliver.upton@linux.dev>,
	Joey Gouly <joey.gouly@arm.com>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Shuah Khan <shuah@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, linux-doc@vger.kernel.org,
	linux-kernel@vger.kernel.org, kvmarm@lists.linux.dev,
	linux-kselftest@vger.kernel.org
Subject: Re: [PATCH 0/3] arm64: Support FEAT_LSFE (Large System Float Extension)
Date: Mon, 30 Jun 2025 11:21:14 +0100	[thread overview]
Message-ID: <ee89d23e-db04-4646-a556-27117e94b5ed@arm.com> (raw)
In-Reply-To: <20250627-arm64-lsfe-v1-0-68351c4bf741@kernel.org>

Hi Mark,

On 6/27/25 18:20, Mark Brown wrote:
> FEAT_LSFE is optional from v9.5, it adds new instructions for atomic
> memory operations with floating point values.  We have no immediate use
> for it in kernel, provide a hwcap so userspace can discover it and allow
> the ID register field to be exposed to KVM guests.
> 
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> Mark Brown (3):
>        arm64/hwcap: Add hwcap for FEAT_LSFE
>        KVM: arm64: Expose FEAT_LSFE to guests
>        kselftest/arm64: Add lsfe to the hwcaps test
> 
>   Documentation/arch/arm64/elf_hwcaps.rst   |  4 ++++
>   arch/arm64/include/asm/hwcap.h            |  1 +
>   arch/arm64/include/uapi/asm/hwcap.h       |  1 +
>   arch/arm64/kernel/cpufeature.c            |  2 ++
>   arch/arm64/kernel/cpuinfo.c               |  1 +
>   arch/arm64/kvm/sys_regs.c                 |  4 +++-
>   tools/testing/selftests/arm64/abi/hwcap.c | 21 +++++++++++++++++++++
>   7 files changed, 33 insertions(+), 1 deletion(-)


I have looked through the series and it looks good to me modulo a couple 
of minor comments left on the patches. Bare in mind fairly new here and 
this is the first use of hwcap3 so I expect more experienced review is 
required.

Reviewed-by: Ben Horgan <ben.horgan@arm.com>

> ---
> base-commit: 86731a2a651e58953fc949573895f2fa6d456841
> change-id: 20250625-arm64-lsfe-0810cf98adc2
> 
> Best regards,
> --
> Mark Brown <broonie@kernel.org>
> 
> 


Thanks,

Ben


      parent reply	other threads:[~2025-06-30 10:21 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-27 17:20 [PATCH 0/3] arm64: Support FEAT_LSFE (Large System Float Extension) Mark Brown
2025-06-27 17:20 ` [PATCH 1/3] arm64/hwcap: Add hwcap for FEAT_LSFE Mark Brown
2025-06-30 10:05   ` Ben Horgan
2025-06-27 17:20 ` [PATCH 2/3] KVM: arm64: Expose FEAT_LSFE to guests Mark Brown
2025-06-27 17:20 ` [PATCH 3/3] kselftest/arm64: Add lsfe to the hwcaps test Mark Brown
2025-06-30 10:08   ` Ben Horgan
2025-06-30 10:21 ` Ben Horgan [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=ee89d23e-db04-4646-a556-27117e94b5ed@arm.com \
    --to=ben.horgan@arm.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=corbet@lwn.net \
    --cc=joey.gouly@arm.com \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=maz@kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=shuah@kernel.org \
    --cc=suzuki.poulose@arm.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;
as well as URLs for NNTP newsgroup(s).