virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy Fitzhardinge <jeremy@goop.org>
To: "Eric W. Biederman" <ebiederm@xmission.com>
Cc: Andrew Morton <akpm@osdl.org>,
	Virtualization <virtualization@lists.osdl.org>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Ian Campbell <Ian.Campbell@XenSource.com>
Subject: Re: [PATCH] Translate asm version of ELFNOTE macro into	preprocessor macro
Date: Wed, 23 Aug 2006 10:47:46 -0700	[thread overview]
Message-ID: <44EC94C2.9080608@goop.org> (raw)
In-Reply-To: <m1sljnml73.fsf@ebiederm.dsl.xmission.com>

Eric W. Biederman wrote:
> 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.
>>>
>>>       

I remember now why I decided to use the assembler macro rather than 
cpp.  The macro names the section after the note name (".note.NAME"), 
and it needs to be quoted so that the name can have spaces and other 
characters which would otherwise upset the assembler.  I couldn't work 
out a clean way to do this with the C preprocessor, since "as" doesn't 
support string concatenation like C does.


> 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. 

Isn't it enough that each entry start have the alignment?  But you need 
some kind of end marker to get the size of the desc field regardless.


>  Being able to
> push and pop a section wouldn't hurt either. 

Yes, I think having each note contain its own .pushsection/popsection is 
the cleaner way of doing it.


    J

  reply	other threads:[~2006-08-23 17:47 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
2006-08-23 17:47         ` Jeremy Fitzhardinge [this message]
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=44EC94C2.9080608@goop.org \
    --to=jeremy@goop.org \
    --cc=Ian.Campbell@XenSource.com \
    --cc=akpm@osdl.org \
    --cc=ebiederm@xmission.com \
    --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).