From: Jeremy Fitzhardinge <jeremy@goop.org>
To: Roland McGrath <roland@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 6/7] Add /sys/kernel/notes
Date: Wed, 11 Jul 2007 19:41:15 -0700 [thread overview]
Message-ID: <469594CB.8090705@goop.org> (raw)
In-Reply-To: <20070712004249.A59D84D0555@magilla.localdomain>
Roland McGrath wrote:
> The earlier patches in this series change the linker script to place it
> appropriately and set the phdr. It's allocated when its input sections are
> allocated. Current builds I've seen don't have any input note sections at
> all. My motivation is for the ld --build-id support, which generates an
> allocated note section as if it were input.
>
OK, I see.
>> I have a patch to always do this, and also convert all the note
>> generation to C code rather than asm. If your patch works for you,
>> however, it should be completely orthogonal.
>>
>
> What note generation do you mean? The only explicit notes in asm that I
> know of are in the vDSO images, not in vmlinux. This patch has nothing to
> do with any vDSO image's generation.
>
I'm adding other notes for Xen, so I have some in my tree. But the vdso
ones could also be generated in C rather than asm. I'm not sure what
stage the patch to convert vsyscall-notes to using linux/elfnote.h is
at; I think its in Andi's tree.
J
prev parent reply other threads:[~2007-07-12 2:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-11 19:04 [PATCH 6/7] Add /sys/kernel/notes Roland McGrath
2007-07-11 19:16 ` Linus Torvalds
2007-07-11 20:51 ` Roland McGrath
2007-07-11 21:45 ` Linus Torvalds
2007-07-11 22:04 ` Roland McGrath
2007-07-11 22:17 ` Linus Torvalds
2007-07-11 22:42 ` Roland McGrath
2007-07-11 22:48 ` Linus Torvalds
2007-07-11 23:45 ` Andrew Morton
2007-07-12 0:37 ` Roland McGrath
2007-07-11 23:57 ` Jeremy Fitzhardinge
2007-07-12 0:42 ` Roland McGrath
2007-07-12 2:41 ` Jeremy Fitzhardinge [this message]
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=469594CB.8090705@goop.org \
--to=jeremy@goop.org \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@redhat.com \
--cc=torvalds@linux-foundation.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