On Tue, 27 Dec 2022 14:20:40 +0000, Mark Brown wrote: > When SME support was merged support for TPIDR2 in signal frames was > omitted, meaning that it was not possible for signal handers to inspect > or modify it. This will present an issue for programs using signals to > implement lightweight threads so let's provide access to TPIDR2 in > signal handlers. > > Implement a new record type for TPIDR2 using the same format as we use > for ESR and add coverage to make sure that this appears in the signal > context as expected. Due to TPIDR2 being reserved for libc we only > validate that the value is unchanged, meaning we're likely to just be > validating the default value of 0 on current systems. I have tested with > a modified version that sets an explicit value. > > [...] Applied to arm64 (for-next/tpidr2), thanks! [1/4] arm64/sme: Document ABI for TPIDR2 signal information https://git.kernel.org/arm64/c/17d0c4a27b2a [2/4] arm64/signal: Include TPIDR2 in the signal context https://git.kernel.org/arm64/c/39e54499280f [3/4] kselftest/arm64: Add TPIDR2 to the set of known signal context records https://git.kernel.org/arm64/c/bae393dabf35 [4/4] kselftest/arm64: Add test case for TPIDR2 signal frame records https://git.kernel.org/arm64/c/8ced92801935 I'll look at the signal handling clean-up patches as well but they probably conflicts with this series and may need to be rebased on top. -- Catalin