From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>,
Christian Borntraeger <borntraeger@de.ibm.com>,
David Hildenbrand <david@redhat.com>,
libvir-list@redhat.com, Jiri Denemark <jdenemar@redhat.com>,
"Jason J. Herne" <jjherne@linux.vnet.ibm.com>,
Markus Armbruster <armbru@redhat.com>,
Richard Henderson <rth@twiddle.net>,
Igor Mammedov <imammedo@redhat.com>,
Eric Blake <eblake@redhat.com>
Subject: [Qemu-devel] [PATCH v2 0/4] target-i386: Implement query-cpu-model-expansion
Date: Mon, 16 Jan 2017 19:11:20 -0200 [thread overview]
Message-ID: <20170116211124.29245-1-ehabkost@redhat.com> (raw)
This series implements query-cpu-model-expansion on target-i386.
Changes v1 -> v2:
-----------------
This version is highly simplified compared to v1. It contains
only an implementation that will return a limited set of
properties. I have a follow-up series that will expend type=full
expansion to return every single QOM property, but this version
will return the same data for type=static and type=full expansion
for simplicity (except that type=static expansion will use the
"base" CPU model as base).
This means this version also won't include "pmu" and
"host-cache-info" in full expansion, and won't require special
code for those properties.
The unit test code was also removed in this version, to keep the
series simple and easier to review. Most of the patches on the
previous series were changes just to make the test case work. I
will send the test-case-related changes as a follow-up series.
---
Cc: Cornelia Huck <cornelia.huck@de.ibm.com>
Cc: Christian Borntraeger <borntraeger@de.ibm.com>
Cc: David Hildenbrand <david@redhat.com>
Cc: libvir-list@redhat.com
Cc: Jiri Denemark <jdenemar@redhat.com>
Cc: "Jason J. Herne" <jjherne@linux.vnet.ibm.com>
Cc: Markus Armbruster <armbru@redhat.com>
Cc: Richard Henderson <rth@twiddle.net>
Cc: Igor Mammedov <imammedo@redhat.com>
Cc: Eric Blake <eblake@redhat.com>
Eduardo Habkost (4):
target-i386: Reorganize and document CPUID initialization steps
qapi-schema: Comment about full expansion of non-migration-safe models
target-i386: Define static "base" CPU model
target-i386: Implement query-cpu-model-expansion QMP command
qapi-schema.json | 9 ++
target/i386/cpu-qom.h | 2 +
monitor.c | 4 +-
target/i386/cpu.c | 317 ++++++++++++++++++++++++++++++++++++++++++++------
4 files changed, 298 insertions(+), 34 deletions(-)
--
2.11.0.259.g40922b1
next reply other threads:[~2017-01-16 21:11 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 21:11 Eduardo Habkost [this message]
2017-01-16 21:11 ` [Qemu-devel] [PATCH v2 1/4] target-i386: Reorganize and document CPUID initialization steps Eduardo Habkost
2017-02-22 18:46 ` Eduardo Habkost
2017-01-16 21:11 ` [Qemu-devel] [PATCH v2 2/4] qapi-schema: Comment about full expansion of non-migration-safe models Eduardo Habkost
2017-02-22 18:49 ` Eduardo Habkost
2017-01-16 21:11 ` [Qemu-devel] [PATCH v2 3/4] target-i386: Define static "base" CPU model Eduardo Habkost
2017-01-16 21:11 ` [Qemu-devel] [PATCH v2 4/4] target-i386: Implement query-cpu-model-expansion QMP command 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=20170116211124.29245-1-ehabkost@redhat.com \
--to=ehabkost@redhat.com \
--cc=armbru@redhat.com \
--cc=borntraeger@de.ibm.com \
--cc=cornelia.huck@de.ibm.com \
--cc=david@redhat.com \
--cc=eblake@redhat.com \
--cc=imammedo@redhat.com \
--cc=jdenemar@redhat.com \
--cc=jjherne@linux.vnet.ibm.com \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=rth@twiddle.net \
/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).