From: ebiederm@xmission.com (Eric W. Biederman)
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Andi Kleen <ak@muc.de>, Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, virtualization@lists.osdl.org,
xen-devel@lists.xensource.com, Chris Wright <chrisw@sous-sol.org>,
Zachary Amsden <zach@vmware.com>,
Ian Campbell <Ian.Campbell@XenSource.com>
Subject: Re: [patch 16/21] Xen-paravirt: Add code into head.S to handle being booted by Xen
Date: Wed, 14 Feb 2007 19:41:37 -0700 [thread overview]
Message-ID: <m1sld8m9b2.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <45D3C42C.1020005@goop.org> (Jeremy Fitzhardinge's message of "Wed, 14 Feb 2007 18:23:40 -0800")
Jeremy Fitzhardinge <jeremy@goop.org> writes:
> Eric W. Biederman wrote:
>> I'm pretty certain we explicitly drop the weird GNU note that
>> is automatically generated by gcc and specifies something informational.
>>
> But that's something else again, since it appears as a PT_GNU_STACK phdr.
Not that. It's more like abi version or gcc version or something
like. At least there used to be one of those notes in every .o file
and compiled program.
>> I don't think anything we are doing is wrong but ld gets confused easily
>> in the corner cases. I'm modestly surprised we didn't have to mark our
>> .note.xxx scions as ".section .note.xxx @note" or whatever the proper
>> gas syntax is.
>
> I did try that, and it didn't make a difference. The manual says that
> the output section type follows the input section type, so I agree its a
> bit surprising we ever get a SHT_NOTE out of it without the @note stuff.
Right. So the surprise is that SHT_NOTE got set. There are some
defaults based on the section name somewhere that appear to have done
the right thing.
My best hunch really is that ld treated the .note sections normally
and just mist the handling of the magic SHT_NOTE type. Which is why
I'm not to worried.
Eric
next prev parent reply other threads:[~2007-02-15 2:43 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20070213221729.772002682@goop.org>
[not found] ` <20070213221829.929261125@goop.org>
2007-02-13 22:39 ` [patch 06/21] Xen-paravirt: remove ctor for pgd cache Zachary Amsden
[not found] ` <20070213221830.466651996@goop.org>
2007-02-13 22:45 ` [patch 13/21] Xen-paravirt: Add nosegneg capability to the vsyscall page notes Zachary Amsden
2007-02-13 22:49 ` Jeremy Fitzhardinge
2007-02-13 22:54 ` Zachary Amsden
2007-02-13 23:13 ` Jeremy Fitzhardinge
2007-02-14 5:38 ` [Xen-devel] " Rusty Russell
[not found] ` <20070213221830.542511707@goop.org>
2007-02-13 22:53 ` [patch 14/21] Xen-paravirt: Add XEN config options and disable unsupported config options Dan Hecht
2007-02-13 23:29 ` Jeremy Fitzhardinge
2007-02-13 23:58 ` [Xen-devel] " Zachary Amsden
2007-02-13 23:58 ` Dan Hecht
[not found] ` <20070213221830.238235953@goop.org>
2007-02-14 1:06 ` [patch 10/21] Xen-paravirt: Name: dont export paravirt_ops structure, do individual functions Zachary Amsden
2007-02-14 1:16 ` Jeremy Fitzhardinge
2007-02-14 1:18 ` Zachary Amsden
2007-02-14 1:37 ` Jeremy Fitzhardinge
2007-02-14 1:43 ` Zachary Amsden
2007-02-14 1:44 ` Jeremy Fitzhardinge
2007-02-14 5:51 ` Rusty Russell
2007-02-14 19:36 ` Christoph Hellwig
[not found] ` <20070213221829.845132535@goop.org>
2007-02-14 1:23 ` [patch 05/21] Xen-paravirt: paravirt_ops: allocate a fixmap slot Dan Hecht
2007-02-14 1:36 ` Jeremy Fitzhardinge
2007-02-14 2:34 ` Dan Hecht
2007-02-14 8:43 ` Gerd Hoffmann
2007-02-14 8:37 ` [Xen-devel] " Jan Beulich
2007-02-14 9:15 ` Andi Kleen
[not found] ` <20070213221829.513618819@goop.org>
2007-02-14 9:24 ` [patch 02/21] Xen-paravirt: Handle a zero-sized VT console Gerd Hoffmann
[not found] ` <20070213221830.707197267@goop.org>
2007-02-13 23:54 ` [patch 16/21] Xen-paravirt: Add code into head.S to handle being booted by Xen Andi Kleen
2007-02-14 0:39 ` Jeremy Fitzhardinge
2007-02-14 8:56 ` [Xen-devel] " Jan Beulich
2007-02-14 18:53 ` Jeremy Fitzhardinge
2007-02-14 20:10 ` Eric W. Biederman
2007-02-14 20:41 ` Jeremy Fitzhardinge
2007-02-14 21:06 ` Eric W. Biederman
2007-02-15 0:13 ` Jeremy Fitzhardinge
2007-02-15 1:39 ` Eric W. Biederman
2007-02-15 1:52 ` Jeremy Fitzhardinge
2007-02-15 2:18 ` Eric W. Biederman
2007-02-15 2:23 ` Jeremy Fitzhardinge
2007-02-15 2:41 ` Eric W. Biederman [this message]
2007-02-14 20:33 ` Eric W. Biederman
2007-02-14 20:42 ` Jeremy Fitzhardinge
[not found] ` <20070213221831.150207238@goop.org>
2007-02-14 20:40 ` [patch 21/21] Xen-paravirt: Add the Xen virtual network device driver Eric W. Biederman
[not found] ` <20070213221830.619562494@goop.org>
2007-02-14 20:45 ` [patch 15/21] Xen-paravirt: Add Xen interface header files Eric W. Biederman
2007-02-15 0:10 ` Jeremy Fitzhardinge
2007-02-15 17:32 ` Christoph Hellwig
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=m1sld8m9b2.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=Ian.Campbell@XenSource.com \
--cc=ak@muc.de \
--cc=akpm@osdl.org \
--cc=chrisw@sous-sol.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.org \
--cc=xen-devel@lists.xensource.com \
--cc=zach@vmware.com \
/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;
as well as URLs for NNTP newsgroup(s).