public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Mark Rutland <mark.rutland@arm.com>
To: Will Deacon <will@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org, broonie@kernel.org,
	catalin.marinas@arm.com, daniel.kiss@arm.com,
	david.spickett@arm.com, luis.machado@arm.com, maz@kernel.org,
	richard.sandiford@arm.com, sander.desmalen@arm.com,
	tabba@google.com, tamas.petz@arm.com, tkjos@google.com,
	yury.khrustalev@arm.com
Subject: Re: [PATCH 13/20] arm64/fpsimd: Make clone() compatible with ZA lazy saving
Date: Wed, 7 May 2025 16:22:06 +0100	[thread overview]
Message-ID: <aBt6nvRmk1O_easH@J2N7QTR9R3> (raw)
In-Reply-To: <20250507145800.GC2475@willie-the-truck>

On Wed, May 07, 2025 at 03:58:01PM +0100, Will Deacon wrote:
> On Tue, May 06, 2025 at 04:25:16PM +0100, Mark Rutland wrote:
> > @@ -441,14 +449,39 @@ int copy_thread(struct task_struct *p, const struct kernel_clone_args *args)
> >  				childregs->sp = stack_start;
> >  		}
> >  
> > +		/*
> > +		 * Due to the AAPCS64 "ZA lazy saving scheme", PSTATE.ZA and
> > +		 * TPIDR2 need to be manipulated as a pair, and either both
> > +		 * need to be inherited or both need to be reset.
> > +		 *
> > +		 * Within a process, child threads must not inherit their
> > +		 * parent's TPIDR2 value or they may clobber their parent's
> > +		 * stack at some later point.
> > +		 *
> > +		 * When a process is fork()'d, the child must inherit ZA and
> > +		 * TPIDR2 from its parent in case there was dormant ZA state.
> > +		 *
> > +		 * Use CLONE_VM to determine when the child will share the
> > +		 * address space with the parent, and cannot safely inherit the
> > +		 * state.
> > +		 */
> > +		if (system_supports_sme()) {
> > +			if (!(clone_flags & CLONE_VM)) {
> > +				p->thread.tpidr2_el0 = read_sysreg_s(SYS_TPIDR2_EL0);
> 
> Why do we need to re-read this register given that we did this just a few
> lines earlier?

Sorry -- I had meant to delete the earlier read. My intent was to centralise
manipulation of TPIDR2 (and ZA) in this block so that it was clear that they
were manipulated as a pair.

I will delete the earlier read, and make this:

| if (system_supports_sme()) {
| 	if (!(clone_flags & CLONE_VM)) {
| 		p->thread.tpidr2_el0 = read_sysreg_s(SYS_TPIDR2_EL0);
| 		ret = copy_thread_za(p, current);
| 		if (ret)
| 			return ret;
| 	} else {
| 		p->thread.tpidr2_el0 = 0;
| 		WARN_ON_ONCE(p->thread.svcr & SVCR_ZA_MASK);
| 	}
| }

... or I can clear TPIDR2 in arch_dup_task_struct() along with ZA, delete the
earlier read here, and make this:

| if (system_supports_sme() && !(clone_flags & CLONE_VM)) {
| 	p->thread.tpidr2_el0 = read_sysreg_s(SYS_TPIDR2_EL0);
| 	ret = copy_thread_za(p, current);
| 	if (ret)
| 		return ret;
| }

Any preference?

[...]

> > diff --git a/tools/testing/selftests/arm64/abi/tpidr2.c b/tools/testing/selftests/arm64/abi/tpidr2.c

> Thank you for updating the selftest, but please can you put it in a
> separate patch?

Sure; I'll factor all the selftest changes out into separate patches.

Mark.


  reply	other threads:[~2025-05-07 15:55 UTC|newest]

Thread overview: 44+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-06 15:25 [PATCH 00/20] arm64: FPSIMD/SVE/SME fixes + re-eanble SME Mark Rutland
2025-05-06 15:25 ` [PATCH 01/20] kselftest/arm64: fp-ptrace: Fix expected FPMR value when PSTATE.SM is changed Mark Rutland
2025-05-06 15:25 ` [PATCH 02/20] arm64/fpsimd: Do not discard modified SVE state Mark Rutland
2025-05-06 15:25 ` [PATCH 03/20] arm64/fpsimd: signal: Clear PSTATE.SM when restoring FPSIMD frame only Mark Rutland
2025-05-07 12:46   ` Will Deacon
2025-05-07 14:01     ` Mark Rutland
2025-05-07 14:39       ` Will Deacon
2025-05-06 15:25 ` [PATCH 04/20] arm64/fpsimd: signal: Mandate SVE payload for streaming-mode state Mark Rutland
2025-05-07  0:59   ` Mark Brown
2025-05-07 12:59   ` Will Deacon
2025-05-07 14:21     ` Mark Rutland
2025-05-07 14:29       ` Will Deacon
2025-05-07 15:02         ` Mark Rutland
2025-05-07 16:14           ` Will Deacon
2025-05-06 15:25 ` [PATCH 05/20] arm64/fpsimd: ptrace: Consistently handle partial writes to NT_ARM_(S)SVE Mark Rutland
2025-05-06 15:25 ` [PATCH 06/20] arm64/fpsimd: Clarify sve_sync_*() functions Mark Rutland
2025-05-06 15:25 ` [PATCH 07/20] arm64/fpsimd: Factor out {sve,sme}_state_size() helpers Mark Rutland
2025-05-06 15:25 ` [PATCH 08/20] arm64/fpsimd: Add task_smstop_sm() Mark Rutland
2025-05-06 15:25 ` [PATCH 09/20] arm64/fpsimd: signal: Use SMSTOP behaviour in setup_return() Mark Rutland
2025-05-06 15:25 ` [PATCH 10/20] arm64/fpsimd: Remove redundant task->mm check Mark Rutland
2025-05-06 15:25 ` [PATCH 11/20] arm64/fpsimd: Consistently preserve FPSIMD state during clone() Mark Rutland
2025-05-06 15:25 ` [PATCH 12/20] arm64/fpsimd: Clear PSTATE.SM " Mark Rutland
2025-05-06 15:25 ` [PATCH 13/20] arm64/fpsimd: Make clone() compatible with ZA lazy saving Mark Rutland
2025-05-07 14:58   ` Will Deacon
2025-05-07 15:22     ` Mark Rutland [this message]
2025-05-07 16:11       ` Will Deacon
2025-05-07 17:21         ` Mark Rutland
2025-05-07 15:57   ` Yury Khrustalev
2025-05-06 15:25 ` [PATCH 14/20] arm64/fpsimd: ptrace/prctl: Ensure VL changes do not resurrect stale data Mark Rutland
2025-05-06 15:25 ` [PATCH 15/20] arm64/fpsimd: ptrace/prctl: Ensure VL changes leave task in a valid state Mark Rutland
2025-05-07 16:12   ` Will Deacon
2025-05-07 17:10     ` Mark Rutland
2025-05-08 10:31       ` Will Deacon
2025-05-06 15:25 ` [PATCH 16/20] arm64/fpsimd: ptrace: Save task state before generating SVE header Mark Rutland
2025-05-06 15:25 ` [PATCH 17/20] arm64/fpsimd: ptrace: Do not present register data for inactive mode Mark Rutland
2025-05-06 15:25 ` [PATCH 18/20] arm64/fpsimd: ptrace: Mandate SVE payload for streaming-mode state Mark Rutland
2025-05-07  1:09   ` Mark Brown
2025-05-06 15:25 ` [PATCH 19/20] arm64/fpsimd: ptrace: Gracefully handle errors Mark Rutland
2025-05-07 16:32   ` Will Deacon
2025-05-08 12:12     ` Mark Rutland
2025-05-06 15:25 ` [PATCH 20/20] arm64/fpsimd: Allow CONFIG_ARM64_SME to be selected Mark Rutland
2025-05-07  1:48 ` [PATCH 00/20] arm64: FPSIMD/SVE/SME fixes + re-eanble SME Mark Brown
2025-05-07  9:56   ` Mark Rutland
2025-05-07 11:26     ` Mark Brown

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=aBt6nvRmk1O_easH@J2N7QTR9R3 \
    --to=mark.rutland@arm.com \
    --cc=broonie@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=daniel.kiss@arm.com \
    --cc=david.spickett@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=luis.machado@arm.com \
    --cc=maz@kernel.org \
    --cc=richard.sandiford@arm.com \
    --cc=sander.desmalen@arm.com \
    --cc=tabba@google.com \
    --cc=tamas.petz@arm.com \
    --cc=tkjos@google.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