From: Michael Ellerman <mpe@ellerman.id.au>
To: Jinglin Wen <jinglin.wen@shingroup.cn>, npiggin@gmail.com
Cc: masahiroy@kernel.org, linux-kernel@vger.kernel.org,
christophe.leroy@csgroup.eu, naveen.n.rao@linux.ibm.com,
linuxppc-dev@lists.ozlabs.org, jinglin.wen@shingroup.cn
Subject: Re: [PATCH] powerpc: Fixed duplicate copying in the early boot.
Date: Mon, 17 Jun 2024 21:28:19 +1000 [thread overview]
Message-ID: <87le336c6k.fsf@mail.lhotse> (raw)
In-Reply-To: <20240617023509.5674-1-jinglin.wen@shingroup.cn>
Jinglin Wen <jinglin.wen@shingroup.cn> writes:
> According to the code logic, when the kernel is loaded to address 0,
> no copying operation should be performed, but it is currently being
> done.
>
> This patch fixes the issue where the kernel code was incorrectly
> duplicated to address 0 when booting from address 0.
>
> Signed-off-by: Jinglin Wen <jinglin.wen@shingroup.cn>
> ---
> arch/powerpc/kernel/head_64.S | 4 +++-
> 1 file changed, 3 insertions(+), 1 deletion(-)
Thanks for the improved change log.
The subject could probably still be clearer, maybe:
Fix unnecessary copy to 0 when kernel is booted at address 0
Looks like this was introduced by:
Fixes: b270bebd34e3 ("powerpc/64s: Run at the kernel virtual address earlier in boot")
Cc: stable@vger.kernel.org # v6.4+
Let me know if you think otherwise.
Just out of interest, how are you hitting this bug? AFAIK none of our
"normal" boot loaders will load the kernel at 0.
> diff --git a/arch/powerpc/kernel/head_64.S b/arch/powerpc/kernel/head_64.S
> index 4690c219bfa4..6c73551bdc50 100644
> --- a/arch/powerpc/kernel/head_64.S
> +++ b/arch/powerpc/kernel/head_64.S
> @@ -647,7 +647,9 @@ __after_prom_start:
> * Note: This process overwrites the OF exception vectors.
> */
> LOAD_REG_IMMEDIATE(r3, PAGE_OFFSET)
> - mr. r4,r26 /* In some cases the loader may */
> + tophys(r4,r26)
> + cmplwi cr0,r4,0 /* runtime base addr is zero */
> + mr r4,r26 /* In some cases the loader may */
> beq 9f /* have already put us at zero */
That is a pretty minimal fix, but I think the code would be clearer if
we just compared the source and destination addresses.
Something like the diff below. Can you confirm that works for you.
cheers
diff --git a/arch/powerpc/kernel/head_64.S b/arch/powerpc/kernel/head_64.S
index 4690c219bfa4..6ad1435303f9 100644
--- a/arch/powerpc/kernel/head_64.S
+++ b/arch/powerpc/kernel/head_64.S
@@ -647,8 +647,9 @@ __after_prom_start:
* Note: This process overwrites the OF exception vectors.
*/
LOAD_REG_IMMEDIATE(r3, PAGE_OFFSET)
- mr. r4,r26 /* In some cases the loader may */
- beq 9f /* have already put us at zero */
+ mr r4, r26 // Load the source address into r4
+ cmpld cr0, r3, r4 // Check if source == dest
+ beq 9f // If so skip the copy
li r6,0x100 /* Start offset, the first 0x100 */
/* bytes were copied earlier. */
next prev parent reply other threads:[~2024-06-17 11:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-17 2:35 [PATCH] powerpc: Fixed duplicate copying in the early boot Jinglin Wen
2024-06-17 11:28 ` Michael Ellerman [this message]
2024-06-18 9:34 ` Jinglin Wen
2024-06-17 16:13 ` Segher Boessenkool
2024-06-18 9:40 ` Jinglin Wen
2024-06-18 12:12 ` Michael Ellerman
2024-06-18 13:27 ` Segher Boessenkool
2024-06-20 2:41 ` [PATCH v2] powerpc: Fix unnecessary copy to 0 when kernel is booted at address 0 Jinglin Wen
2024-06-24 12:30 ` Michael Ellerman
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=87le336c6k.fsf@mail.lhotse \
--to=mpe@ellerman.id.au \
--cc=christophe.leroy@csgroup.eu \
--cc=jinglin.wen@shingroup.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=masahiroy@kernel.org \
--cc=naveen.n.rao@linux.ibm.com \
--cc=npiggin@gmail.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;
as well as URLs for NNTP newsgroup(s).