From: ebiederm@xmission.com (Eric W. Biederman)
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Yinghai Lu <yinghai@kernel.org>, Ingo Molnar <mingo@elte.hu>,
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 18:36:57 -0700 [thread overview]
Message-ID: <m1mybu40qu.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <49B5AD6A.2020101@goop.org> (Jeremy Fitzhardinge's message of "Mon\, 09 Mar 2009 16\:59\:38 -0700")
Jeremy Fitzhardinge <jeremy@goop.org> writes:
> 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?).
It is more that in vmlinux_32.lds.S they needed to be section relative, to
deal with relocation.
For the 64bit kernel the relocation happens at the level under the page table
so does not show up in vmlinux_64.lds.S. Which means it was probably
laziness that didn't get it changed simply because it hasn't matter.
Eric
next prev parent reply other threads:[~2009-03-10 1:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-09 23:59 Absolute symbols in vmlinux_64.lds.S 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 [this message]
-- strict thread matches above, loose matches on Subject: below --
2009-03-10 4:37 Jeremy Fitzhardinge
2009-03-10 5:32 ` Yinghai Lu
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=m1mybu40qu.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=x86@kernel.org \
--cc=yinghai@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox