All of lore.kernel.org
 help / color / mirror / Atom feed
From: Yinghai Lu <yinghai@kernel.org>
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Ingo Molnar <mingo@elte.hu>,
	"Eric W. Biederman" <ebiederm@xmission.com>,
	the arch/x86 maintainers <x86@kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: Absolute symbols in vmlinux_64.lds.S
Date: Mon, 09 Mar 2009 22:32:25 -0700	[thread overview]
Message-ID: <49B5FB69.2020909@kernel.org> (raw)
In-Reply-To: <3k2vgeyfr0tl8gef3ia8o9rh.1236659870536@email.android.com>

Jeremy Fitzhardinge wrote:
> 
> Yinghai Lu <yinghai@kernel.org> wrote:
> 
>> Jeremy Fitzhardinge wrote:
>>> Why does vmlinux_64.lds.S use absolute symbols for things like
>>> __bss_start/stop:
>>>
>>>  __bss_start = .;        /* BSS */
>>>  .bss : AT(ADDR(.bss) - LOAD_OFFSET) {
>>>     *(.bss.page_aligned)
>>>     *(.bss)
>>>     }
>>>  __bss_stop = .;
>>>
>>>
>>> vmlinux_32.lds.S puts __bss_start/stop into the .bss section itself.  Is
>>> there some particular reason they need to be absolute symbols
>>> (relocation?).
>>>
>> they are the same.
> 
> Do you mean it makes no difference?

Sure. System.map should tell the value after the building.

YH

  reply	other threads:[~2009-03-10  5:33 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-10  4:37 Absolute symbols in vmlinux_64.lds.S Jeremy Fitzhardinge
2009-03-10  5:32 ` Yinghai Lu [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-03-09 23:59 Jeremy Fitzhardinge
2009-03-10  1:23 ` Yinghai Lu
2009-03-10  5:37   ` Sam Ravnborg
2009-03-10  5:49     ` Eric W. Biederman
2009-03-10 20:20       ` H. Peter Anvin
2009-03-10 21:25         ` Eric W. Biederman
2009-03-10 22:26           ` Jeremy Fitzhardinge
2009-03-10  5:57     ` Yinghai Lu
2009-03-10 11:24       ` Sam Ravnborg
2009-03-10  1:36 ` Eric W. Biederman

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=49B5FB69.2020909@kernel.org \
    --to=yinghai@kernel.org \
    --cc=ebiederm@xmission.com \
    --cc=jeremy@goop.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=x86@kernel.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.