From: Paolo Bonzini <pbonzini@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@redhat.com>
Cc: qemu-devel <qemu-devel@nongnu.org>,
"P. Berrange, Daniel" <berrange@redhat.com>,
"Blake, Eric" <eblake@redhat.com>,
"Armbruster, Markus" <armbru@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 2/3] qobject: assume base of a qobject is at offset 0
Date: Wed, 21 Mar 2018 17:23:57 +0100 [thread overview]
Message-ID: <2da23a16-51c7-fdcc-dfc5-7eed08f60d6f@redhat.com> (raw)
In-Reply-To: <CAMxuvawM+oOH7wHEMdcjJAZVaL9PbjfHA+UfMLu5+SbZgchrTw@mail.gmail.com>
On 21/03/2018 17:11, Marc-André Lureau wrote:
> Hi
>
> On Wed, Mar 21, 2018 at 5:00 PM, Paolo Bonzini <pbonzini@redhat.com> wrote:
>> On 21/03/2018 16:55, Marc-André Lureau wrote:
>>> That would work with an anonymous union though:
>>>
>>> struct QObject {
>>> union {
>>> QType type;
>>> QType base;
>>> };
>>> size_t refcnt;
>>> };
>>>
>>> If it's acceptable, I think I'll take this approach.
>>
>> You don't need QEMU_GENERIC at all then, don't you?
>
> Ah ah, that's what I thought too, but the type of QObject * &x->base
> isn't QObject * :)
>
> I don't think we can fool it there (without loosing some type safety)
Hmm, perhaps by making it "struct {} base"?
Or even:
struct QObjectCommon {
QType type;
size_t refcnt;
}
struct QObject {
QObjectCommon base;
}
struct QString {
QObjectCommon base;
...
}
Paolo
next prev parent reply other threads:[~2018-03-21 16:24 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-21 13:40 [Qemu-devel] [PATCH 0/3] RFC: simplify qobject refcount Marc-André Lureau
2018-03-21 13:40 ` [Qemu-devel] [PATCH 1/3] compiler: extend QEMU_GENERIC to handle more arguments Marc-André Lureau
2018-03-21 13:40 ` [Qemu-devel] [PATCH 2/3] qobject: assume base of a qobject is at offset 0 Marc-André Lureau
2018-03-21 14:01 ` Paolo Bonzini
2018-03-21 14:08 ` Marc-André Lureau
2018-03-21 14:19 ` Eric Blake
2018-03-21 14:21 ` Marc-André Lureau
2018-03-21 14:49 ` Paolo Bonzini
2018-03-21 15:29 ` Eric Blake
2018-03-21 15:34 ` Paolo Bonzini
2018-03-21 15:55 ` Marc-André Lureau
2018-03-21 16:00 ` Paolo Bonzini
2018-03-21 16:11 ` Marc-André Lureau
2018-03-21 16:23 ` Paolo Bonzini [this message]
2018-03-21 16:59 ` Marc-André Lureau
2018-03-21 17:08 ` Eric Blake
2018-03-21 17:23 ` Marc-André Lureau
2018-03-21 17:38 ` Eric Blake
2018-03-21 17:43 ` Paolo Bonzini
2018-03-21 14:01 ` Eric Blake
2018-03-21 14:02 ` Paolo Bonzini
2018-03-21 13:40 ` [Qemu-devel] [PATCH 3/3] qobject: replace qobject_incref/QINCREF qobject_decref/QDECREF Marc-André Lureau
2018-03-21 14:28 ` Eric Blake
2018-03-21 14:51 ` Marc-André Lureau
2018-03-21 15:36 ` Eric Blake
2018-03-21 14:09 ` [Qemu-devel] [PATCH 0/3] RFC: simplify qobject refcount Eric Blake
2018-03-21 14:19 ` Marc-André Lureau
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=2da23a16-51c7-fdcc-dfc5-7eed08f60d6f@redhat.com \
--to=pbonzini@redhat.com \
--cc=armbru@redhat.com \
--cc=berrange@redhat.com \
--cc=eblake@redhat.com \
--cc=marcandre.lureau@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).