From: Catalin Marinas <catalin.marinas@arm.com>
To: linux-arm-kernel@lists.infradead.org,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>
Cc: broonie@kernel.org, daniel.kiss@arm.com, maz@kernel.org,
richard.sandiford@arm.com, sander.desmalen@arm.com,
tamas.petz@arm.com, yury.khrustalev@arm.com
Subject: Re: [PATCH] arm64/fpsimd: signal: Clear TPIDR2 when delivering signals
Date: Mon, 28 Apr 2025 20:25:54 +0100 [thread overview]
Message-ID: <174586835122.250615.2378305002313638533.b4-ty@arm.com> (raw)
In-Reply-To: <20250417190113.3778111-1-mark.rutland@arm.com>
On Thu, 17 Apr 2025 20:01:13 +0100, Mark Rutland wrote:
> Linux is intended to be compatible with userspace written to Arm's
> AAPCS64 procedure call standard [1,2]. For the Scalable Matrix Extension
> (SME), AAPCS64 was extended with a "ZA lazy saving scheme", where SME's
> ZA tile is lazily callee-saved and caller-restored. In this scheme,
> TPIDR2_EL0 indicates whether the ZA tile is live or has been saved by
> pointing to a "TPIDR2 block" in memory, which has a "za_save_buffer"
> pointer. This scheme has been implemented in GCC and LLVM, with
> necessary runtime support implemented in glibc.
>
> [...]
Applied to arm64 (for-next/sme-fixes), thanks!
[1/1] arm64/fpsimd: signal: Clear TPIDR2 when delivering signals
https://git.kernel.org/arm64/c/b376108e1f88
--
Catalin
prev parent reply other threads:[~2025-04-28 19:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-17 19:01 [PATCH] arm64/fpsimd: signal: Clear TPIDR2 when delivering signals Mark Rutland
2025-04-24 10:18 ` Mark Rutland
2025-04-28 19:25 ` 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=174586835122.250615.2378305002313638533.b4-ty@arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=daniel.kiss@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=richard.sandiford@arm.com \
--cc=sander.desmalen@arm.com \
--cc=tamas.petz@arm.com \
--cc=will@kernel.org \
--cc=yury.khrustalev@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