From: "Daniel P. Berrange" <berrange@redhat.com>
To: Valentin Rakush <valentin.rakush@gmail.com>
Cc: asmetanin@virtuozzo.com, den@openvz.org, qemu-devel@nongnu.org,
ehabkost@redhat.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [RFC] target-i386: Display i386 CPUID properties
Date: Tue, 12 Jan 2016 14:50:20 +0000 [thread overview]
Message-ID: <20160112145019.GN17626@redhat.com> (raw)
In-Reply-To: <1452609387-7232-1-git-send-email-valentin.rakush@gmail.com>
On Tue, Jan 12, 2016 at 05:36:27PM +0300, Valentin Rakush wrote:
> This is RFC because implementation depends on the upcoming class
> properties
> http://lists.nongnu.org/archive/html/qemu-devel/2015-08/msg03115.html
> and also because this patch does not handle all x86_64 properties.
>
> This RFC is in response to concerns pointed in this review but with changed
> subject line as recommended.
> http://lists.nongnu.org/archive/html/qemu-devel/2016-01/msg00053.html
>
> This RFC demonstrates the way for displaying cpu properties using -cpu
> help option.
The point of doing this with QOM class properties, is such that we can
create a facility to query class properties for any QOM type in a
consistent manner. I was expecting this would take the form of a
QMP monitor command 'qom-type-properties' or something along those
lines.
Regards,
Daniel
--
|: http://berrange.com -o- http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org -o- http://virt-manager.org :|
|: http://autobuild.org -o- http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org -o- http://live.gnome.org/gtk-vnc :|
next prev parent reply other threads:[~2016-01-12 14:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 14:36 [Qemu-devel] [RFC] target-i386: Display i386 CPUID properties Valentin Rakush
2016-01-12 14:50 ` Daniel P. Berrange [this message]
2016-01-14 15:36 ` Valentin Rakush
2016-01-23 14:01 ` Eduardo Habkost
2016-01-25 8:50 ` Valentin Rakush
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=20160112145019.GN17626@redhat.com \
--to=berrange@redhat.com \
--cc=afaerber@suse.de \
--cc=asmetanin@virtuozzo.com \
--cc=den@openvz.org \
--cc=ehabkost@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=valentin.rakush@gmail.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 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.