All of lore.kernel.org
 help / color / mirror / Atom feed
From: zyxsjl@126.com (zyxsjl)
To: linux-arm-kernel@lists.infradead.org
Subject: abt kernel 2.6 compressed/head.s
Date: Tue, 27 Oct 2009 11:54:24 +0800 (CST)	[thread overview]
Message-ID: <18250270.157661256615664391.JavaMail.coremail@bj126app51.126.com> (raw)

 
 hi anyone, 
I have not understood some code in this file below: 
    #ifndef CONFIG_ZBOOT_ROM
  /*
* If we're running fully PIC === CONFIG_ZBOOT_ROM = n,
* we need to fix up pointers into the BSS region.
  * r2 - BSS start
  * r3 - BSS end
  * sp - stack pointer
  */
  add r2, r2, r0
  add r3, r3, r0
  add sp, sp, r0
  /*
  * Relocate all entries in the GOT table.
  */
1: ldr r1, [r6, #0] @ relocate entries in the GOT
add r1, r1, r0 @ table. This fixes up the
  str r1, [r6], #4 @ C references.
  cmp r6, ip
  blo 1b
#else
  /*
* Relocate entries in the GOT table. We only relocate
* the entries that are outside the (relocated) BSS region.
  */
1: ldr r1, [r6, #0] @ relocate entries in the GOT
  cmp r1, r2 @ entry < bss_start ||
  cmphs r3, r1   @ _end < entry
addlo r1, r1, r0 @ table. This fixes up the
  str r1, [r6], #4 @ C references.
  cmp r6, ip
  blo 1b
#endif
my question is:what is the different between the both CONFIG_ZBOOT_ROM=y or n, and so led to the different tackles from the above code on relocation?
 thanks ahead
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20091027/78b61379/attachment-0001.htm>

             reply	other threads:[~2009-10-27  3:54 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-10-27  3:54 zyxsjl [this message]
2009-10-27 18:06 ` abt kernel 2.6 compressed/head.s Russell King - ARM Linux
  -- strict thread matches above, loose matches on Subject: below --
2009-10-25  6:49 zyxsjl

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=18250270.157661256615664391.JavaMail.coremail@bj126app51.126.com \
    --to=zyxsjl@126.com \
    --cc=linux-arm-kernel@lists.infradead.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.