All of lore.kernel.org
 help / color / mirror / Atom feed
From: Goswin von Brederlow <goswin-v-b@web.de>
To: grub-devel@gnu.org
Subject: Re: [PATCH] ARM U-Boot BSS zeroing
Date: Tue, 14 May 2013 15:02:31 +0200	[thread overview]
Message-ID: <20130514130231.GC27079@frosties> (raw)
In-Reply-To: <20130513153729.GL28516@rocoto.smurfnet.nu>

On Mon, May 13, 2013 at 03:37:32PM +0000, Leif Lindholm wrote:
> The import into the collaborative branch discarded the call to
> get_real_bss_start before starting the BSS zeroing operation.
> 
> While get_real_bss_start might have been a bit of an ugly hack,
> simply discarding it means that we now end up doing unaligned
> STR operations, and any platform with MMU disabled fails to boot.
> 
> The attached patch prepends a bytewise zeroing loop until
> word-aligned, and then continue as before.
> 
> /
>     Leif

> === modified file 'grub-core/kern/arm/uboot/startup.S'
> --- grub-core/kern/arm/uboot/startup.S	2013-05-03 13:07:39 +0000
> +++ grub-core/kern/arm/uboot/startup.S	2013-05-13 14:59:43 +0000
> @@ -100,7 +100,13 @@
>  	@ Since we _are_ the C run-time, we need to manually zero the BSS
>  	@ region before continuing
>  	ldr	r0, =EXT_C(__bss_start)	@ zero from here
> -	ldr	r1, =EXT_C(_end)		@ to here
> +	@ If unaligned, bytewise zero until base address aligned.
> +	mov	r1, #0
> +1:	tst	r0, #3
> +	beq	2f
> +	strb	r1, [r0], #1
> +	b	1b
> +2:	ldr	r1, =EXT_C(_end)		@ to here
>  	mov	r2, #0
>  1:	str	r2, [r0], #4
>  	cmp	r0, r1

What if I have a 1 byte BSS aligned at 1 byte? You would zero 3 bytes
and overshoot _end and then what happens after the cmp in the last line?

MfG
	Goswin


  parent reply	other threads:[~2013-05-14 13:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-13 15:37 [PATCH] ARM U-Boot BSS zeroing Leif Lindholm
2013-05-13 16:09 ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-05-14 13:02 ` Goswin von Brederlow [this message]
2013-05-14 16:09   ` Vladimir 'phcoder' Serbinenko

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=20130514130231.GC27079@frosties \
    --to=goswin-v-b@web.de \
    --cc=grub-devel@gnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.