From: Gerd Hoffmann <kraxel@redhat.com>
To: Juan Quintela <quintela@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Re: [RfC PATCH] qdev: rework device properties.
Date: Tue, 30 Jun 2009 16:19:06 +0200 [thread overview]
Message-ID: <4A4A1EDA.2010700@redhat.com> (raw)
In-Reply-To: <m3y6r9byz3.fsf@neno.mitica>
On 06/30/09 16:03, Juan Quintela wrote:
> Gerd Hoffmann<kraxel@redhat.com> wrote:
>> Early RfC patch. Not functional yet. Just for comments right now.
>>
>> Overall plan:
>> * drop property lists. The properties are saved directly in the
>> device state structs instead.
>> * drop qdev_get_prop* functions, not needed any more.
>> * replace qdev_set_prop* functions by qdev_prop_{parse,set*}.
>>
>> Done:
>> * added code to handle properties.
>>
>> Todo:
>> * convert all the device drivers.
>> * actually drop the old functions.
>
> Any good reason why you remove the list of propierties?
Pointless indirection and extra storage.
Note that this doesn't mean properties itself go away.
> a- a way to defino an alias, that "mouse" is equivalent to "QEMU USB
> Keyboard". One is the qdev name and the other is the name passed to
> --usbdevice name.
stick an alias next to name in DeviceInfo?
I don't see why this should use properties.
> b- things like disk are composed of:
> "disk" : "rest of disk arguments"
No. You'll create the host state from most of "rest of disk arguments".
You'll attach a name property to qdev so the driver has a handle to
lookup the host side of things.
cheers,
Gerd
prev parent reply other threads:[~2009-06-30 14:19 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-30 11:31 [Qemu-devel] [RfC PATCH] qdev: rework device properties Gerd Hoffmann
2009-06-30 14:03 ` [Qemu-devel] " Juan Quintela
2009-06-30 14:15 ` Paul Brook
2009-06-30 14:49 ` Juan Quintela
2009-06-30 15:11 ` Paul Brook
2009-06-30 14:19 ` Gerd Hoffmann [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=4A4A1EDA.2010700@redhat.com \
--to=kraxel@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=quintela@redhat.com \
/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).