mirror of https://lore.kernel.org/lkml/
 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 1/3] arm64/hwcap: Add hwcap for FEAT_LSFE
Date: Mon, 30 Jun 2025 11:05:18 +0100	[thread overview]
Message-ID: <77dd46da-85ea-442a-a05e-d54c56b51786@arm.com> (raw)
In-Reply-To: <20250627-arm64-lsfe-v1-1-68351c4bf741@kernel.org>



On 6/27/25 18:20, Mark Brown wrote:
> FEAT_LSFE (Large System Float Extension), providing atomic floating point
> memory operations, is optional from v9.5. This feature adds no new
> architectural stare and we have no immediate use for it in the kernel so
> simply provide a hwcap for it to support discovery by userspace.

nit: s/stare/state/

Thanks,

Ben


  reply	other threads:[~2025-06-30 10:05 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 [this message]
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 ` [PATCH 0/3] arm64: Support FEAT_LSFE (Large System Float Extension) Ben Horgan

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=77dd46da-85ea-442a-a05e-d54c56b51786@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
all inboxes | Powered by JetHome®