From: "Michael S. Tsirkin" <mst@redhat.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RfC PATCH 2/2] qdev/prop: convert pci.c to helper macros.
Date: Fri, 31 Jul 2009 17:32:51 +0300 [thread overview]
Message-ID: <20090731143251.GA9233@redhat.com> (raw)
In-Reply-To: <1249045499-10973-3-git-send-email-kraxel@redhat.com>
On Fri, Jul 31, 2009 at 03:04:59PM +0200, Gerd Hoffmann wrote:
>
> Signed-off-by: Gerd Hoffmann <kraxel@redhat.com>
> ---
> hw/pci.c | 9 ++-------
> hw/pci.h | 2 +-
> 2 files changed, 3 insertions(+), 8 deletions(-)
>
> diff --git a/hw/pci.c b/hw/pci.c
> index 4d0cdc7..27eac04 100644
> --- a/hw/pci.c
> +++ b/hw/pci.c
> @@ -60,13 +60,8 @@ static struct BusInfo pci_bus_info = {
> .size = sizeof(PCIBus),
> .print_dev = pcibus_dev_print,
> .props = (Property[]) {
> - {
> - .name = "addr",
> - .info = &qdev_prop_pci_devfn,
> - .offset = offsetof(PCIDevice, devfn),
> - .defval = (uint32_t[]) { -1 },
> - },
> - {/* end of list */}
> + DEFINE_PROP_PCI_DEVFN("addr", PCIDevice, devfn, -1),
> + DEFINE_PROP_END_OF_LIST()
> }
I think the type safety is an important addition.
Unfortunately there's still duplication - in the macro definition:
DEFINE_PROP_DEFAULT(_n, _s, _f, _d, qdev_prop_uint64, uint64_t)
which leaves room for mistakes. And there will have to be lots of these
macros, for each type.
Here's an idea: if each property exposed a "type" field, documenting
what type it supports, we could use that for a type-safe macro. Along
the lines of:
- .info = &qdev_prop_pci_devfn,
- .offset = offsetof(PCIDevice, devfn),
+ QDEV_INFO(&qdev_prop_pci_devfn, PCIDevice, devfn),
Where QDEV_INFO would be defined as something like:
#define QDEV_INFO(_prop, _struct, _field) \
.info = (_prop), \
.offset = (offsetof(_struct, _field) + ( 0 && \
(long)(&(_prop)->type - &((_struct *)0)->_field)) \
)
Defval could be checked in a similar fashion.
This seems to be free of gcc extensions and gives more or less sane errors like:
foo.c:26: error: invalid operands to binary - (have ‘long long int *’ and ‘int *’)
This way we need only 1 or 2 macros that everyone can use.
> };
>
> diff --git a/hw/pci.h b/hw/pci.h
> index cbfea6a..a2ec16a 100644
> --- a/hw/pci.h
> +++ b/hw/pci.h
> @@ -177,7 +177,7 @@ struct PCIDevice {
>
> /* the following fields are read only */
> PCIBus *bus;
> - int devfn;
> + uint32_t devfn;
Good catch - with int the value could get sign-extended if we try
to decode just the high bits by >>, and shows importance of
type-checking.
> char name[64];
> PCIIORegion io_regions[PCI_NUM_REGIONS];
>
> --
> 1.6.2.5
>
Full self-contained toy example below, in case you want to play with
my idea some more:
#include <stdio.h>
#include <stddef.h>
struct prop {
long long type;
};
struct desc {
struct prop *info;
int offset;
};
struct foo {
int bar1;
long long bar2;
};
#define QDEV_INFO(_prop, _struct, _field) \
.info = (_prop), \
.offset = (offsetof(_struct, _field) + ( 0 && \
(long)(&(_prop)->type - &((_struct *)0)->_field) \
))
struct prop prop1;
struct desc desc1 = {
QDEV_INFO(&prop1, struct foo, bar2)
};
int main()
{
printf("offset: %d\n", desc1.offset);
return 0;
}
next prev parent reply other threads:[~2009-07-31 14:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 13:04 [Qemu-devel] [RfC PATCH 0/2] qdev/prop: macros for creating typechecked properties Gerd Hoffmann
2009-07-31 13:04 ` [Qemu-devel] [RfC PATCH 1/2] " Gerd Hoffmann
2009-07-31 13:04 ` [Qemu-devel] [RfC PATCH 2/2] qdev/prop: convert pci.c to helper macros Gerd Hoffmann
2009-07-31 14:32 ` Michael S. Tsirkin [this message]
2009-07-31 15:01 ` Gerd Hoffmann
2009-07-31 15:42 ` 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=20090731143251.GA9233@redhat.com \
--to=mst@redhat.com \
--cc=kraxel@redhat.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).