From: Catalin Marinas <catalin.marinas@arm.com>
To: Will Deacon <will@kernel.org>, Shuah Khan <shuah@kernel.org>,
Mark Brown <broonie@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kselftest@vger.kernel.org, linux-kernel@vger.kernel.org,
Mark Rutland <mark.rutland@arm.com>
Subject: Re: [PATCH v2 0/3] kselftest/arm64: fp-ptrace enhancements
Date: Tue, 12 Nov 2024 16:07:34 +0000 [thread overview]
Message-ID: <173142698242.893467.659853152392768670.b4-ty@arm.com> (raw)
In-Reply-To: <20241112-arm64-fp-ptrace-fpmr-v2-0-250b57c61254@kernel.org>
On Tue, 12 Nov 2024 13:08:13 +0000, Mark Brown wrote:
> This series contains a bit of a grab bag of improvements to the floating
> point tests, mainly fp-ptrace. Globally over all the tests we start
> using defines from the generated sysregs (following the example of the
> KVM selftests) for SVCR, stop being quite so wasteful with registers
> when calling into the assembler code then expand the coverage of both ZA
> writes and FPMR (which was not there since fp-ptrace and the 2023 dpISA
> extensions were on the list at the same time).
>
> [...]
Applied to arm64 (for-next/kselftest), thanks!
[1/3] kselftets/arm64: Use flag bits for features in fp-ptrace assembler code
https://git.kernel.org/arm64/c/c0350076c13e
[2/3] kselftest/arm64: Expand the set of ZA writes fp-ptrace does
https://git.kernel.org/arm64/c/7e9c5b00009a
[3/3] kselftest/arm64: Add FPMR coverage to fp-ptrace
https://git.kernel.org/arm64/c/7dbd26d0b22d
--
Catalin
prev parent reply other threads:[~2024-11-12 16:07 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-12 13:08 Mark Brown
2024-11-12 13:08 ` [PATCH v2 1/3] kselftets/arm64: Use flag bits for features in fp-ptrace assembler code Mark Brown
2024-11-12 13:08 ` [PATCH v2 2/3] kselftest/arm64: Expand the set of ZA writes fp-ptrace does Mark Brown
2024-11-12 13:08 ` [PATCH v2 3/3] kselftest/arm64: Add FPMR coverage to fp-ptrace Mark Brown
2024-11-12 13:26 ` Catalin Marinas
2024-11-12 13:38 ` Mark Brown
2024-11-12 16:07 ` Catalin Marinas [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=173142698242.893467.659853152392768670.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=shuah@kernel.org \
--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®