From: ebiederm@xmission.com (Eric W. Biederman)
To: Jeremy Fitzhardinge <jeremy@goop.org>
Cc: Ian Campbell <Ian.Campbell@XenSource.com>,
Andrew Morton <akpm@osdl.org>,
Virtualization <virtualization@lists.osdl.org>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Translate asm version of ELFNOTE macro into preprocessor macro
Date: Wed, 23 Aug 2006 11:11:12 -0600 [thread overview]
Message-ID: <m1sljnml73.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <44EC72F3.70505@goop.org> (Jeremy Fitzhardinge's message of "Wed, 23 Aug 2006 08:23:31 -0700")
Jeremy Fitzhardinge <jeremy@goop.org> writes:
> Ian Campbell wrote:
>>> OK, seems reasonable. Eric Biederman solved this by having NOTE/ENDNOTE (or
>>> something like that) in his "bzImage with ELF header" patch, but I don't
>>> remember it being used in any way which is incompatible with using a CPP
>>> macro.
>>>
>>
>> I can't find that patch, does NOTE/ENDNOTE just do the push/pop .note
>> section?
>>
>> That would solve the problem with the first argument of the macro being
>> a string but the final argument could still be for .asciz note contents.
>>
>
> It looks like:
>
> .macro note name, type
> .balign 4
> .int 2f - 1f # n_namesz
> .int 4f - 3f # n_descsz
> .int \type # n_type
> .balign 4
> 1: .asciz "\name"
> 2: .balign 4
> 3:
> .endm
> .macro enote
> 4: .balign 4
> .endm
>
>
> so it allows you to put arbitrary stuff in the desc part of the note. The
> downside is that its a little more cumbersome syntactically for the common case.
I don't expect it to be much more cumbersome, as two pieces, and you need the extra
alignment at the end to ensure each not entry is 4 byte aligned. Being able to
push and pop a section wouldn't hurt either.
Eric
next prev parent reply other threads:[~2006-08-23 17:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-23 11:49 [PATCH] Translate asm version of ELFNOTE macro into preprocessor macro Ian Campbell
2006-08-23 14:49 ` Jeremy Fitzhardinge
2006-08-23 15:14 ` Ian Campbell
2006-08-23 15:23 ` Jeremy Fitzhardinge
2006-08-23 17:11 ` Eric W. Biederman [this message]
2006-08-23 17:47 ` Jeremy Fitzhardinge
2006-08-23 19:43 ` Ian Campbell
2006-08-23 21:02 ` Jeremy Fitzhardinge
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=m1sljnml73.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=Ian.Campbell@XenSource.com \
--cc=akpm@osdl.org \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=virtualization@lists.osdl.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;
as well as URLs for NNTP newsgroup(s).