From: ebiederm@xmission.com (Eric W. Biederman)
To: "H. Peter Anvin" <hpa@kernel.org>
Cc: Sam Ravnborg <sam@ravnborg.org>, Yinghai Lu <yinghai@kernel.org>,
Jeremy Fitzhardinge <jeremy@goop.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: Tue, 10 Mar 2009 14:25:18 -0700 [thread overview]
Message-ID: <m1k56x2hq9.fsf@fess.ebiederm.org> (raw)
In-Reply-To: <49B6CB84.8060404@kernel.org> (H. Peter Anvin's message of "Tue\, 10 Mar 2009 13\:20\:20 -0700")
"H. Peter Anvin" <hpa@kernel.org> writes:
> Eric W. Biederman wrote:
>>
>> I have no complaint with that. I believe the symbols are absolute
>> simply because they were originally coded that way and the relocatable
>> kernel work on x86_64 didn't need them to change.
>>
>
> I have a vague memory of a bug in the x86-64 ld.
Oh. I'm certain of it. ld has all kinds of bugs off and on,
occasionally we are bound to run into a few of them.
ld bugs isn't the reason for using absolute linker symbols. We use a
bunch of relative linker symbols as well. All of the generic linker
scripts sections use them as well as a few of the x86_64 specific
sections.
For crazy things like 0 relative per cpu sections it might matter.
For the rest of the symbols absolute or relative simply
doesn't matter.
Is anyone interested in writing a patch testing it and changing things?
If not things should be good enough for now.
Eric
next prev parent reply other threads:[~2009-03-10 21:25 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 [this message]
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
-- 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=m1k56x2hq9.fsf@fess.ebiederm.org \
--to=ebiederm@xmission.com \
--cc=hpa@kernel.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=sam@ravnborg.org \
--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