From: Eduardo Habkost <ehabkost@redhat.com>
To: Igor Mammedov <imammedo@redhat.com>
Cc: qemu-devel@nongnu.org, Marcel Apfelbaum <marcel@redhat.com>,
Paolo Bonzini <pbonzini@redhat.com>,
Markus Armbruster <armbru@redhat.com>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [Qemu-devel] [PATCH 1/4] machine: Register TYPE_MACHINE properties as class properties
Date: Fri, 14 Oct 2016 10:24:25 -0300 [thread overview]
Message-ID: <20161014132425.GE3275@thinpad.lan.raisama.net> (raw)
In-Reply-To: <20161014150830.7caab068@nial.brq.redhat.com>
On Fri, Oct 14, 2016 at 03:08:30PM +0200, Igor Mammedov wrote:
> On Thu, 13 Oct 2016 18:26:39 -0300
> Eduardo Habkost <ehabkost@redhat.com> wrote:
>
> > When doing the conversion, the NULL errp arguments on the
> > property registration calls were changed to &error_abort.
> >
> > Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
> So many property registrations look pretty ugly but still
> better than doing it per instance, not that it matters
> so far as there is only 1 instance of Machine at a time.
>
> So
> Reviewed-by: Igor Mammedov <imammedo@redhat.com>
Thanks!
>
> most of the properties below are dumb field setter/getter,
> it would be much better to declare them statically and
> make generic Object code to initialize them at type
> initialization time.
> i.e. make similar thing like static properties but for class
> and probably extend it to have optional custom setter/getter.
I've been considering doing that. It should be easier after the
"qdev class properties" series gets applied, but the existing
static-property code is still specific to DeviceState (probably
it's only because the static property getter/setters include a
dev->realized check).
--
Eduardo
next prev parent reply other threads:[~2016-10-14 13:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-13 21:26 [Qemu-devel] [PATCH 0/4] machine, hostmem, pc: Register properties as class properties Eduardo Habkost
2016-10-13 21:26 ` [Qemu-devel] [PATCH 1/4] machine: Register TYPE_MACHINE " Eduardo Habkost
2016-10-14 13:08 ` Igor Mammedov
2016-10-14 13:24 ` Eduardo Habkost [this message]
2016-10-13 21:26 ` [Qemu-devel] [PATCH 2/4] pc: Register TYPE_PC_MACHINE " Eduardo Habkost
2016-10-14 12:27 ` Igor Mammedov
2016-10-13 21:26 ` [Qemu-devel] [PATCH 3/4] hostmem: Register TYPE_MEMORY_BACKEND " Eduardo Habkost
2016-10-14 12:09 ` Igor Mammedov
2016-10-13 21:26 ` [Qemu-devel] [PATCH 4/4] hostmem-file: Register TYPE_MEMORY_BACKEND_FILE " Eduardo Habkost
2016-10-14 12:16 ` Igor Mammedov
2016-10-14 1:01 ` [Qemu-devel] [PATCH 0/4] machine, hostmem, pc: Register " no-reply
2016-10-14 15:13 ` Eduardo Habkost
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=20161014132425.GE3275@thinpad.lan.raisama.net \
--to=ehabkost@redhat.com \
--cc=armbru@redhat.com \
--cc=imammedo@redhat.com \
--cc=marcel@redhat.com \
--cc=mst@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.