From: Will Deacon <will@kernel.org>
To: Bradley Morgan <include@grrlz.net>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] arm64: sleep: dedup the sleep_save_stash slot lookup
Date: Fri, 17 Jul 2026 12:31:03 +0100 [thread overview]
Message-ID: <aloSd8AwZQPoh4ev@willie-the-truck> (raw)
In-Reply-To: <EFA466A8-F9E9-422D-B10D-BC1B324050AC@grrlz.net>
On Thu, Jul 16, 2026 at 05:55:38PM +0100, Bradley Morgan wrote:
> On July 16, 2026 3:35:48 PM GMT+01:00, Will Deacon <will@kernel.org> wrote:
> >On Sun, Jul 05, 2026 at 07:23:31PM +0000, Bradley Morgan wrote:
> >> Both __cpu_suspend_enter() and _cpu_resume() open code the same MPIDR
> >> hash lookup. Factor it into a get_sleep_stash_slot macro.
> >>
> >> Signed-off-by: Bradley Morgan <include@grrlz.net>
> >> ---
> >> arch/arm64/kernel/sleep.S | 55 +++++++++++++++++++++------------------
> >> 1 file changed, 30 insertions(+), 25 deletions(-)
> >>
> >> diff --git a/arch/arm64/kernel/sleep.S b/arch/arm64/kernel/sleep.S
> >> index e112b8537f10..8820a131aef7 100644
> >> --- a/arch/arm64/kernel/sleep.S
> >> +++ b/arch/arm64/kernel/sleep.S
> >> @@ -64,6 +64,31 @@
> >> lsr \mask ,\mask, \rs3
> >> orr \dst, \dst, \mask // dst|=(aff3>>rs3)
> >> .endm
> >> +
> >> +/*
> >> + * Compute the address of the current CPU's entry in sleep_save_stash,
> >> + * i.e. &sleep_save_stash[hash(MPIDR_EL1)].
> >> + *
> >> + * @slot: output register
> >> + *
> >> + * Clobbers: x2 - x8
> >> + */
> >> + .macro get_sleep_stash_slot slot
> >> + mpidr_hash_assert_distinct \slot, x2
> >> + mrs x3, mpidr_el1
> >> + adr_l x2, mpidr_hash
> >> + ldr x8, [x2, #MPIDR_HASH_MASK]
> >> + /*
> >> + * Following code relies on the struct mpidr_hash
> >> + * members size.
> >> + */
> >> + ldp w4, w5, [x2, #MPIDR_HASH_SHIFTS]
> >> + ldp w6, w7, [x2, #(MPIDR_HASH_SHIFTS + 8)]
> >> + compute_mpidr_hash x2, x4, x5, x6, x7, x3, x8
> >> + ldr_l \slot, sleep_save_stash
> >> + add \slot, \slot, x2, lsl #3
> >> + .endm
> >
> >I think this would now be the only user of compute_mpidr_hash, so it's
> >probably better to inline that macro here and then we don't need to
> >bother with mpidr_hash_assert_distinct at all (i.e. your first patch
> >isn't needed).
> >
> >Will
> >
>
>
> Will! What do you think of this?
I think it's been mangled by your mail client. Please just send a v2 and
I'll get to it on the next pass through my inbox (which is an unholy mess
right now).
Will
prev parent reply other threads:[~2026-07-17 11:31 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-05 19:23 [PATCH 0/2] arm64: sleep: two small compute_mpidr_hash cleanups Bradley Morgan
2026-07-05 19:23 ` [PATCH 1/2] arm64: sleep: assert compute_mpidr_hash registers are distinct Bradley Morgan
2026-07-05 19:23 ` [PATCH 2/2] arm64: sleep: dedup the sleep_save_stash slot lookup Bradley Morgan
2026-07-16 14:35 ` Will Deacon
2026-07-16 16:55 ` Bradley Morgan
2026-07-17 11:31 ` Will Deacon [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=aloSd8AwZQPoh4ev@willie-the-truck \
--to=will@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=include@grrlz.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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