From: Daniel Jacobowitz <drow@false.org>
To: qemu-devel@nongnu.org
Cc: Anthony Liguori <aliguori@us.ibm.com>,
Paul Brook <paul@codesourcery.com>
Subject: Re: [Qemu-devel] [RFC] Introduce module API to QEMU
Date: Fri, 3 Apr 2009 10:04:19 -0400 [thread overview]
Message-ID: <20090403140419.GA23421@caradoc.them.org> (raw)
In-Reply-To: <1238724755-15929-1-git-send-email-aliguori@us.ibm.com>
On Thu, Apr 02, 2009 at 09:12:35PM -0500, Anthony Liguori wrote:
> It uses __attribute__((section)) to make module_init/module_exit work. I looked
> at making this work by using a parser to find and extract all of these things.
> I'm not sure I know a good way to force the names to be unique via CPP but in
> the very least, I came to the determination that I would need to use something
> like perl or python which would introduce a new dependency to the build.
FYI, I'm pretty sure this will not work in a Windows-hosted QEMU.
There's a mandatory minimum alignment for PE/COFF sections and it will
introduce unexpected padding between your array elements. I had to
remove a similar trick from prelink when we ported it to Windows.
Yes, this does raise the question of how __attribute__((constructor))
works. Maybe it's specific to new named sections? Maybe I'm just
misremembering. Anyway, whatever you come up with, testing on
Windows would be a good idea if you haven't already.
--
Daniel Jacobowitz
CodeSourcery
next prev parent reply other threads:[~2009-04-03 14:04 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-03 2:12 [Qemu-devel] [RFC] Introduce module API to QEMU Anthony Liguori
2009-04-03 2:29 ` malc
2009-04-03 3:36 ` Anthony Liguori
2009-04-03 3:48 ` malc
2009-04-03 12:59 ` Anthony Liguori
2009-04-03 17:00 ` malc
2009-04-03 17:31 ` Anthony Liguori
2009-04-03 17:46 ` malc
2009-04-03 17:59 ` M. Warner Losh
2009-04-03 17:58 ` M. Warner Losh
2009-04-03 18:05 ` Anthony Liguori
2009-04-03 20:12 ` Kevin Wolf
2009-04-03 18:30 ` malc
2009-04-03 7:08 ` Mark McLoughlin
2009-04-03 13:01 ` Anthony Liguori
2009-04-03 17:36 ` Anthony Liguori
2009-04-03 7:50 ` Avi Kivity
2009-04-03 11:35 ` Paul Brook
2009-04-03 12:57 ` Anthony Liguori
2009-04-03 13:09 ` Paul Brook
2009-04-03 14:10 ` Anthony Liguori
2009-04-03 14:11 ` Anthony Liguori
2009-04-03 14:28 ` Paul Brook
2009-04-03 14:53 ` Avi Kivity
2009-04-03 16:15 ` Anthony Liguori
2009-04-03 17:12 ` Blue Swirl
2009-04-03 14:04 ` Daniel Jacobowitz [this message]
2009-04-03 14:54 ` Avi Kivity
2009-04-03 15:10 ` Paul Brook
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=20090403140419.GA23421@caradoc.them.org \
--to=drow@false.org \
--cc=aliguori@us.ibm.com \
--cc=paul@codesourcery.com \
--cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.