From: Andrea Bolognani <abologna@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>,
qemu-devel@nongnu.org, Markus Armbruster <armbru@redhat.com>
Subject: Re: [Qemu-devel] [RFC PATCH qemu] qmp: Add qom-list-properties to list QOM object properties
Date: Tue, 23 Jan 2018 14:33:51 +0100 [thread overview]
Message-ID: <1516714431.31897.6.camel@redhat.com> (raw)
In-Reply-To: <20180123124922.GB14832@umbus>
On Tue, 2018-01-23 at 23:49 +1100, David Gibson wrote:
> It's also occurred to me that making a spapr specific approach to this
> might not be quite as horrible as I initially thought. The
> capabilities table is global (and immutable) so coding up a
> "get-spapr-caps" qapi entry point which encodes the stuff there into
> json giving the names and allowed values of each cap would be fairly
> straightforward.
OTOH, qom-list-properties is a superset of device-list-properties
so it could be used instead of it if supported; plus it would
expose properties of machines which are not also capabilities and
properties of non-pSeries machine types. There could be value in
taking the more generic approach.
> Accurately retreiving default values would be trickier, not sure if
> that's important or not.
Not sure. I think it's okay not to expose that information, since
there are other areas where defaults are not exposed and so all
libvirt can do is document that not *explicitly* setting a feature
will result in the hypervisor default, whatever that might happen
to be, being enforced.
--
Andrea Bolognani / Red Hat / Virtualization
next prev parent reply other threads:[~2018-01-23 13:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-19 5:09 [Qemu-devel] [RFC PATCH qemu] qmp: Add qom-list-properties to list QOM object properties Alexey Kardashevskiy
2018-01-19 5:19 ` David Gibson
2018-01-19 6:15 ` Alexey Kardashevskiy
2018-01-19 6:22 ` Alexey Kardashevskiy
2018-01-19 14:34 ` Andrea Bolognani
2018-01-23 10:08 ` Andrea Bolognani
2018-01-23 11:20 ` David Gibson
2018-01-23 12:03 ` Andrea Bolognani
2018-01-23 12:49 ` David Gibson
2018-01-23 13:33 ` Andrea Bolognani [this message]
2018-01-31 9:03 ` Alexey Kardashevskiy
2018-01-31 17:22 ` Markus Armbruster
2018-01-31 17:22 ` Markus Armbruster
2018-02-02 2:02 ` Alexey Kardashevskiy
2018-02-02 7:37 ` Markus Armbruster
2018-02-05 3:30 ` Alexey Kardashevskiy
2018-02-07 12:18 ` Andrea Bolognani
2018-02-21 3:36 ` Alexey Kardashevskiy
2018-02-21 10:01 ` Paolo Bonzini
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=1516714431.31897.6.camel@redhat.com \
--to=abologna@redhat.com \
--cc=aik@ozlabs.ru \
--cc=armbru@redhat.com \
--cc=david@gibson.dropbear.id.au \
--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.