From: Mark Rutland <mark.rutland@arm.com>
To: Bradley Morgan <brads@mainlining.org>
Cc: Will Deacon <will@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
James Morse <james.morse@arm.com>, Marc Zyngier <maz@kernel.org>,
Ard Biesheuvel <ardb@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/7] arm64: head: correct comment for init_kernel_el()
Date: Wed, 2 Sep 2026 14:46:36 +0100 [thread overview]
Message-ID: <apgovCGT-D7OWbSE@J2N7QTR9R3.cambridge.arm.com> (raw)
In-Reply-To: <20260825205839.14571-3-brads@mainlining.org>
On Tue, Aug 25, 2026 at 08:58:34PM +0000, Bradley Morgan wrote:
> The comment above init_kernel_el() still says the function configures
> the CPU to execute at the highest reachable EL, but that stopped being
> true a while back. Ever since commit ae4b7e38e9a94798 ("arm64: Allow
> sticky E2H when entering EL1"), init_kernel_el() always drops to EL1,
> and it is finalise_el2() that brings us back up to EL2 when we want it.
>
> Update the comment to match what the code actually does.
>
> Signed-off-by: Bradley Morgan <brads@mainlining.org>
> Cc: Ard Biesheuvel <ardb@kernel.org>
> Cc: Catalin Marinas <catalin.marinas@arm.com>
> Cc: James Morse <james.morse@arm.com>
> Cc: Marc Zyngier <maz@kernel.org>
> Cc: Will Deacon <will@kernel.org>
> ---
> arch/arm64/kernel/head.S | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
This looks to be my patch [1], but with a (partially) rewritten commit
message, and my S-o-B dropped.
There was admittedly one typo in that commit message that needed to be
fixed, but I don't think the rest of the changes were necessary, and I
don't think it's approriate to drop my S-o-B.
I think similar is true for the rest of the series. The patch fixing the
_cpu_resume() only seems to have a paraphrased commit message.
[1] https://git.kernel.org/pub/scm/linux/kernel/git/mark/linux.git/commit/?id=ee4323ff6a2ba4c3989b38f13b2c1a516d6c27e4
Mark.
>
> diff --git a/arch/arm64/kernel/head.S b/arch/arm64/kernel/head.S
> index 87a822e5c4ca..c6301557eee1 100644
> --- a/arch/arm64/kernel/head.S
> +++ b/arch/arm64/kernel/head.S
> @@ -254,9 +254,9 @@ SYM_FUNC_END(__primary_switched)
> .section ".idmap.text","a"
>
> /*
> - * Starting from EL2 or EL1, configure the CPU to execute at the highest
> - * reachable EL supported by the kernel in a chosen default state. If dropping
> - * from EL2 to EL1, configure EL2 before configuring EL1.
> + * Starting from EL2 or EL1, configure the CPU to execute at EL1.
> + * If dropping from EL2 to EL1, configure EL2 before configuring EL1.
> + * To use VHE we'll upgrade back to EL2 later in finalise_el2().
> *
> * Since we cannot always rely on ERET synchronizing writes to sysregs (e.g. if
> * SCTLR_ELx.EOS is clear), we place an ISB prior to ERET.
> --
> 2.47.3
next prev parent reply other threads:[~2026-09-02 13:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-25 20:58 [PATCH 0/7] arm64: hibernate: dust off the suspend/cleanup rework Bradley Morgan
2026-08-25 20:58 ` [PATCH 1/7] arm64: hibernate: pass HVC_SET_VECTORS args to the resume hvc Bradley Morgan
2026-08-25 20:58 ` [PATCH 2/7] arm64: head: correct comment for init_kernel_el() Bradley Morgan
2026-09-02 13:46 ` Mark Rutland [this message]
2026-09-02 13:49 ` Bradley Morgan
2026-09-02 13:58 ` Mark Rutland
2026-09-02 14:01 ` Bradley Morgan
2026-08-25 20:58 ` [PATCH 3/7] arm64: hibernate: free MTE tag pages after saving Bradley Morgan
2026-08-25 20:58 ` [PATCH 4/7] arm64: hibernate: fix _cpu_resume() calling convention Bradley Morgan
2026-08-25 20:58 ` [PATCH 5/7] arm64: hibernate: use dcache_by_myline_op Bradley Morgan
2026-08-25 20:58 ` [PATCH 6/7] arm64: hibernate: only clean to PoC Bradley Morgan
2026-08-25 20:58 ` [PATCH 7/7] arm64: hibernate: use regular cpu_resume() logic Bradley Morgan
2026-08-28 10:32 ` [PATCH 0/7] arm64: hibernate: dust off the suspend/cleanup rework Ard Biesheuvel
2026-08-28 11:31 ` Bradley Morgan
2026-09-02 13:50 ` Mark Rutland
2026-09-02 13:51 ` Bradley Morgan
2026-09-02 14:03 ` Mark Rutland
2026-09-02 14:06 ` Bradley Morgan
2026-09-03 10:53 ` Will Deacon
2026-09-03 11:26 ` Bradley Morgan
2026-09-03 12:16 ` Will Deacon
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=apgovCGT-D7OWbSE@J2N7QTR9R3.cambridge.arm.com \
--to=mark.rutland@arm.com \
--cc=ardb@kernel.org \
--cc=brads@mainlining.org \
--cc=catalin.marinas@arm.com \
--cc=james.morse@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@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