linux-mips
[Top] [All Lists]

Re: RFC: Sentosa boot fix

To: vagabon.xyz@gmail.com
Subject: Re: RFC: Sentosa boot fix
From: Atsushi Nemoto <anemo@mba.ocn.ne.jp>
Date: Wed, 31 Jan 2007 01:41:33 +0900 (JST)
Cc: macro@linux-mips.org, dan@debian.org, linux-mips@linux-mips.org, ralf@linux-mips.org
In-reply-to: <cda58cb80701290827i1892e74dlb60651847982f77f@mail.gmail.com>
Original-recipient: rfc822;linux-mips@linux-mips.org
References: <Pine.LNX.4.64N.0701291527130.26916@blysk.ds.pg.gda.pl> <20070130.011442.21365159.anemo@mba.ocn.ne.jp> <cda58cb80701290827i1892e74dlb60651847982f77f@mail.gmail.com>
Sender: linux-mips-bounce@linux-mips.org
On Mon, 29 Jan 2007 17:27:04 +0100, "Franck Bui-Huu" <vagabon.xyz@gmail.com> 
wrote:
> It may be interesting to have a look to the assembly code in this case
> to see what the compiler does exactly.

I compiled ip27 kernel and really confused...

head.S:
        PTR_LA          t0, __bss_start         # clear .bss
        LONG_S          zero, (t0)

System.map:
a8000000003b6000 A __bss_start

vmlinux:
a800000000385058:       3c0c003b        lui     t0,0x3b
a80000000038505c:       658c6000        daddiu  t0,t0,24576
a800000000385060:       fd800000        sd      zero,0(t0)

vmlinux.32:
80385058:       3c0c003b        lui     t4,0x3b
8038505c:       658c6000        daddiu  t4,t4,24576
80385060:       fd800000        sd      zero,0(t4)

How does this code work?  Isn't address 0x3b6000 in user space?

---
Atsushi Nemoto

<Prev in Thread] Current Thread [Next in Thread>