From: Eduardo Habkost <ehabkost@redhat.com>
To: qemu-devel@nongnu.org
Subject: [Qemu-devel] [PATCH v2 2/4] qapi-schema: Comment about full expansion of non-migration-safe models
Date: Mon, 16 Jan 2017 19:11:22 -0200 [thread overview]
Message-ID: <20170116211124.29245-3-ehabkost@redhat.com> (raw)
In-Reply-To: <20170116211124.29245-1-ehabkost@redhat.com>
Add a note warning that static expansion may not be 100% accurate
when the CPU model is not migration-safe. This will be the case
on x86 when expansing the "host" CPU model, because there are
"host" features that can't have a migration-safe representation
(e.g. "host-cache-info").
Signed-off-by: Eduardo Habkost <ehabkost@redhat.com>
---
qapi-schema.json | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/qapi-schema.json b/qapi-schema.json
index ce20f16757..33d7ef1274 100644
--- a/qapi-schema.json
+++ b/qapi-schema.json
@@ -3294,6 +3294,15 @@
# migration-safe, but allows tooling to get an insight and work with
# model details.
#
+# Note: When a non-migration-safe CPU model is expanded in static mode, some
+# features enabled by the CPU model may be omitted, because they can't be
+# implemented by a static CPU model definition (e.g. cache info passthrough and
+# PMU passthrough in x86). If you need an accurate representation of the
+# features enabled by a non-migration-safe CPU model, use @full. If you need a
+# static representation that will keep ABI compatibility even when changing QEMU
+# version or machine-type, use @static (but keep in mind that some features may
+# be omitted).
+#
# Since: 2.8.0
##
{ 'enum': 'CpuModelExpansionType',
--
2.11.0.259.g40922b1
next prev parent 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 [Qemu-devel] [PATCH v2 0/4] target-i386: Implement query-cpu-model-expansion Eduardo Habkost
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 ` Eduardo Habkost [this message]
2017-02-22 18:49 ` [Qemu-devel] [PATCH v2 2/4] qapi-schema: Comment about full expansion of non-migration-safe models 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-3-ehabkost@redhat.com \
--to=ehabkost@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 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).