From: Paolo Bonzini <pbonzini@redhat.com>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH v2 00/18] qom: dynamic properties and composition tree (v2)
Date: Mon, 05 Dec 2011 18:01:00 +0100 [thread overview]
Message-ID: <4EDCF8CC.9050804@redhat.com> (raw)
In-Reply-To: <4EDCF38D.70609@codemonkey.ws>
On 12/05/2011 05:38 PM, Anthony Liguori wrote:
>>>
>>
>> -device would use parse/print, not get/set. So it would still use the
>> strings.
>
> I don't want -device to have special knowledge of properties. I want it
> to set the properties are strings. The property implementation is
> private to Object.
Ok, I see where you're coming from with legacy properties too. Yeah,
then it makes sense to rename properties (to legacy<name> perhaps) as
long as the equivalent "name" property is available that uses visitors.
I.e. each qdev property would be registered twice, with two different
names, one for QOM and one for -device.
Paolo
next prev parent reply other threads:[~2011-12-05 17:01 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-03 0:56 [Qemu-devel] [PATCH v2 00/18] qom: dynamic properties and composition tree (v2) Paolo Bonzini
2011-12-03 2:40 ` Anthony Liguori
2011-12-03 14:24 ` Paolo Bonzini
2011-12-03 21:34 ` Anthony Liguori
2011-12-04 21:01 ` Anthony Liguori
2011-12-05 9:52 ` Paolo Bonzini
2011-12-05 14:36 ` Anthony Liguori
2011-12-05 14:50 ` Peter Maydell
2011-12-05 15:04 ` Anthony Liguori
2011-12-05 15:33 ` Peter Maydell
2011-12-05 19:28 ` Anthony Liguori
2011-12-05 15:47 ` Paolo Bonzini
2011-12-05 16:13 ` Anthony Liguori
2011-12-05 16:29 ` Paolo Bonzini
2011-12-05 16:38 ` Anthony Liguori
2011-12-05 17:01 ` Paolo Bonzini [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-12-02 20:20 Anthony Liguori
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=4EDCF8CC.9050804@redhat.com \
--to=pbonzini@redhat.com \
--cc=anthony@codemonkey.ws \
--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.