From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>
Cc: "Claude Opus 4.6" <noreply@anthropic.com>
Subject: Re: [PATCH v2 2/2] ARM: setup_c: avoid clearing BSS twice
Date: Wed, 4 Mar 2026 10:05:38 +0100 [thread overview]
Message-ID: <79efc69c-d161-4dc0-9a95-f6176b7331c7@pengutronix.de> (raw)
In-Reply-To: <20260304-arm-setup-c-v2-2-d26af520ab03@pengutronix.de>
Hi,
On 3/4/26 8:53 AM, Sascha Hauer wrote:
> Add a bss_cleared variable that is set after the first call to
> setup_c(). On subsequent calls, the BSS clear is skipped to avoid
> wiping already-initialized data.
>
> Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
> Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
Reviewed-by: Ahmad Fatoum <a.fatoum@pengutronix.de>
Minor point below:
> +.section .data
.data.bss_cleared or is it already in its own section?
> +bss_cleared:
> + .word 0
> +
> /*
> * void relocate_to_adr(unsigned long targetadr)
> *
> diff --git a/arch/arm/cpu/setupc_64.S b/arch/arm/cpu/setupc_64.S
> index fd95187a04..caa16d3582 100644
> --- a/arch/arm/cpu/setupc_64.S
> +++ b/arch/arm/cpu/setupc_64.S
> @@ -7,19 +7,29 @@
> .section .text.setupc
>
> /*
> - * setup_c: clear bss
> + * setup_c: clear bss if not yet done
> */
> ENTRY(setup_c)
> + adr_l x0, bss_cleared
> + ldr w1, [x0]
> + cbnz w1, 1f /* skip if already done */
> mov x15, x30
> adr_l x0, __bss_start
> mov x1, #0
> adr_l x2, __bss_stop
> sub x2, x2, x0
> bl __memset /* clear bss */
> + adr_l x0, bss_cleared
> + mov w1, #1
> + str w1, [x0] /* mark bss cleared */
> mov x30, x15
> - ret
> +1: ret
> ENDPROC(setup_c)
>
> +.section .data
Same question
> +bss_cleared:
> + .word 0
> +
> /*
> * void relocate_to_adr(unsigned long targetadr)
> *
>
--
Pengutronix e.K. | |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
prev parent reply other threads:[~2026-03-04 9:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-04 7:53 [PATCH v2 0/2] ARM: Avoid to clear bss multiple times Sascha Hauer
2026-03-04 7:53 ` [PATCH v2 1/2] ARM: setupc_32: remove relocation code from setup_c Sascha Hauer
2026-03-04 9:02 ` Ahmad Fatoum
2026-03-04 7:53 ` [PATCH v2 2/2] ARM: setup_c: avoid clearing BSS twice Sascha Hauer
2026-03-04 9:05 ` Ahmad Fatoum [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=79efc69c-d161-4dc0-9a95-f6176b7331c7@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=noreply@anthropic.com \
--cc=s.hauer@pengutronix.de \
/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