From: "Andreas Färber" <afaerber@suse.de>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: Igor Mammedov <imammedo@redhat.com>,
peter.crosthwaite@xilinx.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2] qom: fix inherited interfaces
Date: Tue, 24 Dec 2013 12:26:15 +0100 [thread overview]
Message-ID: <52B96F57.8030007@suse.de> (raw)
In-Reply-To: <52B96D55.50703@redhat.com>
Am 24.12.2013 12:17, schrieb Paolo Bonzini:
> Il 24/12/2013 01:18, Andreas Färber ha scritto:
>> Thanks, I have squashed it, but I would appreciate if someone more
>> familiar with interfaces could take a quick look at my commit message
>> before I send a PULL tomorrow. Should I drop Reported-by during squash?
>>
>> https://github.com/afaerber/qemu-cpu/commits/qom-next
>
> I think it can be left in because the subclass::superclass::interface
> bug was pre-existing. Here is a better wording:
>
> qom: Do not register interface "types" in the type table and fix names
>
> There should be no need to look them up nor enumerate the interface
> "types", whose "classes" are really just vtables. Just create the
> types and add them to the interface list of the parent type.
>
> Interfaces not registering their type anymore means that accessing
> superclass::interface by type name will fail when initializing
> subclass::interface. Thus, we need to pre-initialize the subclass's
> parent_type field before calling type_initialize. Apart from this, the
> interface "types" should never be used and thus it is harmless to leave
> them out of the hashtable.
>
> Further, the interface types had a bug with interfaces that are
> inherited from a superclass: The implementation type name was wrong
> (for example it was subclass::superclass::interface rather than
> just subclass::interface). This patch fixes this as well.
>
> Reported-by: Igor Mammedov <imammedo@redhat.com>
> Tested-by: Igor Mammedov <imammedo@redhat.com>
> Signed-off-by: Paolo Bonzini <pbonzini@redhat.com>
Thanks a lot, updated with one minor change: The initial "them" is now
ambiguous (types vs. names), so I've dropped it since the sentence ends
in "types" anyway.
Andreas
--
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer; HRB 16746 AG Nürnberg
prev parent reply other threads:[~2013-12-24 11:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-20 21:54 [Qemu-devel] [PATCH v2] qom: fix inherited interfaces Paolo Bonzini
2013-12-24 0:18 ` Andreas Färber
2013-12-24 11:17 ` Paolo Bonzini
2013-12-24 11:26 ` Andreas Färber [this message]
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=52B96F57.8030007@suse.de \
--to=afaerber@suse.de \
--cc=imammedo@redhat.com \
--cc=pbonzini@redhat.com \
--cc=peter.crosthwaite@xilinx.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).