From: Anthony Liguori <aliguori@us.ibm.com>
To: Blue Swirl <blauwirbel@gmail.com>
Cc: Gerd Hoffman <kraxel@redhat.com>,
Paul Brook <paul@codesourcery.com>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH 2/2] Introduce macro for defining qdev properties
Date: Fri, 17 Jul 2009 15:05:21 -0500 [thread overview]
Message-ID: <4A60D981.5030008@us.ibm.com> (raw)
In-Reply-To: <f43fc5580907171132x71f65c80pae06a889b4b240ff@mail.gmail.com>
Blue Swirl wrote:
>> I'm not sure how to do this without GCC extensions. We could potentially
>> add macro decorators and use a sparse-like tool to extract property lists
>> automatically from device state.
>>
>
> Then there is the template way:
>
Yes, I also considered that.
Another option would be comment decorators along with a post-processor.
typedef struct MyDeviceStruct
{
SysBusDevice parent;
/* public */
QDEV_PROP(uint32_t, queue_depth);
QDEV_PROP(uint32_t, tx_mitigation_delay);
QDEV_PROP(CharDriverState *, chr);
} MyDeviceStruct;
Normally, we:
#define QDEV_PROP(a, b) a b
But then we could also do something like:
#define QDEV_PROP(a, b) QPROP_CANARY stringify(a) stringify(b)
Then run through CPP and grep 'CANARY | typedef struct' and then parse
the output to build the table at build time.
Of course, we could just do QDEV_PROP like I originally proposed and
then if we ever support something other than GCC, we can introduce a CPP
post-processor to build the tables at compile time.
This is the approach we're taking for constructors after all.
--
Regards,
Anthony Liguori
next prev parent reply other threads:[~2009-07-17 20:05 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-17 14:41 [Qemu-devel] [PATCH 0/2][RFC] Introduce macros for setting properties Anthony Liguori
2009-07-17 14:41 ` [Qemu-devel] [PATCH 1/2] Introduce CharDriverState qdev property type Anthony Liguori
2009-07-21 14:46 ` [Qemu-devel] " Gerd Hoffmann
2009-07-21 14:53 ` Anthony Liguori
2009-07-21 15:03 ` Gerd Hoffmann
2009-07-21 15:14 ` Gerd Hoffmann
2009-07-21 15:23 ` Anthony Liguori
2009-07-21 15:34 ` Gerd Hoffmann
2009-07-21 15:47 ` Anthony Liguori
2009-07-22 9:48 ` Gerd Hoffmann
2009-07-17 14:41 ` [Qemu-devel] [PATCH 2/2] Introduce macro for defining qdev properties Anthony Liguori
2009-07-17 17:23 ` Blue Swirl
2009-07-17 17:26 ` Anthony Liguori
2009-07-17 17:33 ` Paul Brook
2009-07-17 18:11 ` Anthony Liguori
2009-07-17 18:32 ` Blue Swirl
2009-07-17 20:05 ` Anthony Liguori [this message]
2009-07-17 22:58 ` Paul Brook
2009-07-18 12:43 ` Jamie Lokier
2009-07-18 16:13 ` Anthony Liguori
2009-07-20 2:29 ` Jamie Lokier
2009-07-21 8:30 ` [Qemu-devel] " Gerd Hoffmann
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=4A60D981.5030008@us.ibm.com \
--to=aliguori@us.ibm.com \
--cc=blauwirbel@gmail.com \
--cc=kraxel@redhat.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 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).