All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Andreas Färber" <afaerber@suse.de>
To: Markus Armbruster <armbru@redhat.com>
Cc: Paolo Bonzini <pbonzini@redhat.com>, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH RFC 1/7] qom: allow properties to be registered against classes
Date: Thu, 3 Sep 2015 18:41:21 +0200	[thread overview]
Message-ID: <55E87831.5040405@suse.de> (raw)
In-Reply-To: <87oahjmpaw.fsf@blackfin.pond.sub.org>

Am 03.09.2015 um 18:37 schrieb Markus Armbruster:
> "Daniel P. Berrange" <berrange@redhat.com> writes:
>> On Wed, Sep 02, 2015 at 06:18:28PM +0200, Andreas Färber wrote:
>>> I had suggested exactly this looong time ago, but Anthony opposed it. I
>>> don't quite remember why...
>>
>> It is a while back now so I don't remember all aspects of the discussion
>> either. The main thing I remember is that we could not simply use the
>> existing GObject model from glib, since that exclusively records properties
>> against the object class. In some cases, particularly the relationships
>> between objects, QEMU needed to be able to define properties on the fly
>> against object instances.
> 
> I remember Anthony's assertion that this is the case, but I don't
> remember the actual problems where this is actually the case.
> 
> What properties do we currently define that could not be defined against
> the class?

All child<> properties and everything on Container objects.

Cheers,
Andreas

-- 
SUSE Linux GmbH, Maxfeldstr. 5, 90409 Nürnberg, Germany
GF: Felix Imendörffer, Jane Smithard, Graham Norton; HRB 21284 (AG Nürnberg)

  reply	other threads:[~2015-09-03 16:41 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-26 12:03 [Qemu-devel] [PATCH RFC 0/7] Making QOM introspectable Daniel P. Berrange
2015-08-26 12:03 ` [Qemu-devel] [PATCH RFC 1/7] qom: allow properties to be registered against classes Daniel P. Berrange
2015-09-02 16:18   ` Andreas Färber
2015-09-03 15:49     ` Daniel P. Berrange
2015-09-03 16:37       ` Markus Armbruster
2015-09-03 16:41         ` Andreas Färber [this message]
2015-09-03 17:02           ` Markus Armbruster
2015-09-03 17:09             ` Daniel P. Berrange
2015-09-03 17:21               ` Andreas Färber
2015-09-03 17:25                 ` Daniel P. Berrange
2015-09-04  6:56                   ` Markus Armbruster
2015-09-07 12:54                     ` Paolo Bonzini
2015-09-11 16:09     ` Daniel P. Berrange
2015-09-04 21:38   ` Marc-André Lureau
2015-09-07  8:46     ` Daniel P. Berrange
2015-09-07 13:11       ` Andreas Färber
2015-09-07 13:17         ` Daniel P. Berrange
2015-08-26 12:03 ` [Qemu-devel] [PATCH RFC 2/7] hostmem: register properties against the class instead of object Daniel P. Berrange
2015-08-26 12:03 ` [Qemu-devel] [PATCH RFC 3/7] rng: " Daniel P. Berrange
2015-08-26 12:03 ` [Qemu-devel] [PATCH RFC 4/7] tpm: " Daniel P. Berrange
2015-08-26 12:03 ` [Qemu-devel] [PATCH RFC 5/7] cpu: avoid using object instance state in property getter Daniel P. Berrange
2015-08-26 12:03 ` [Qemu-devel] [PATCH RFC 6/7] x86-cpu: register properties against the class instead of object Daniel P. Berrange
2015-08-26 12:03 ` [Qemu-devel] [PATCH RFC 7/7] machine: " Daniel P. Berrange
2015-09-02  9:05 ` [Qemu-devel] [PATCH RFC 0/7] Making QOM introspectable Daniel P. Berrange
2015-09-02 11:14   ` Markus Armbruster
2015-09-02 16:16   ` Andreas Färber

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=55E87831.5040405@suse.de \
    --to=afaerber@suse.de \
    --cc=armbru@redhat.com \
    --cc=pbonzini@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 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.