From: gerg@snapgear•com (Greg Ungerer)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH 01/10] ARM: no need for nommu to jump through the hoops that mmu does
Date: Wed, 6 Oct 2010 15:09:29 +1000 [thread overview]
Message-ID: <4CAC0489.90201@snapgear.com> (raw)
In-Reply-To: <E1P2oXR-00020E-FV@rmk-PC.arm.linux.org.uk>
On 05/10/10 03:09, Russell King - ARM Linux wrote:
> nommu can jump directly to __mmap_switched without the absolute
> address branching which the mmuful kernel does.
>
> Signed-off-by: Russell King<rmk+kernel@arm•linux.org.uk>
Acked-by: Greg Ungerer <gerg@uclinux•org>
> arch/arm/kernel/head-nommu.S | 5 +----
> 1 files changed, 1 insertions(+), 4 deletions(-)
>
> diff --git a/arch/arm/kernel/head-nommu.S b/arch/arm/kernel/head-nommu.S
> index 573b803..814ce1a 100644
> --- a/arch/arm/kernel/head-nommu.S
> +++ b/arch/arm/kernel/head-nommu.S
> @@ -48,8 +48,6 @@ ENTRY(stext)
> movs r8, r5 @ invalid machine (r5=0)?
> beq __error_a @ yes, error 'a'
>
> - ldr r13, __switch_data @ address to jump to after
> - @ the initialization is done
> adr lr, BSYM(__after_proc_init) @ return (PIC) address
> ARM( add pc, r10, #PROCINFO_INITFUNC )
> THUMB( add r12, r10, #PROCINFO_INITFUNC )
> @@ -87,8 +85,7 @@ __after_proc_init:
> mcr p15, 0, r0, c1, c0, 0 @ write control reg
> #endif /* CONFIG_CPU_CP15 */
>
> - mov r3, r13
> - mov pc, r3 @ clear the BSS and jump
> + b __mmap_switched @ clear the BSS and jump
> @ to start_kernel
> ENDPROC(__after_proc_init)
> .ltorg
--
------------------------------------------------------------------------
Greg Ungerer -- Principal Engineer EMAIL: gerg at snapgear.com
SnapGear Group, McAfee PHONE: +61 7 3435 2888
8 Gardner Close FAX: +61 7 3217 5323
Milton, QLD, 4064, Australia WEB: http://www.SnapGear.com
prev parent reply other threads:[~2010-10-06 5:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-10-04 17:09 [PATCH 01/10] ARM: no need for nommu to jump through the hoops that mmu does Russell King - ARM Linux
2010-10-06 5:09 ` Greg Ungerer [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=4CAC0489.90201@snapgear.com \
--to=gerg@snapgear$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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