From: "Daniel P. Berrangé" <berrange@redhat.com>
To: qemu-devel@nongnu.org
Cc: qemu-s390x@nongnu.org, "Thomas Huth" <thuth@redhat.com>,
qemu-arm@nongnu.org, "David Hildenbrand" <david@redhat.com>,
"Cornelia Huck" <cohuck@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: [PATCH 0/3] target: RFC: display deprecation note for '-cpu help'
Date: Thu, 14 Jul 2022 16:07:32 +0100 [thread overview]
Message-ID: <20220714150735.1835166-1-berrange@redhat.com> (raw)
When querying '-cpu help' there is no presentation of fact that a
CPU may be deprecated. The user just has to try it and see if they
get a depecation message at runtime. The QMP command for querying
CPUs report a deprecation bool flag, but not the explanatory
reason.
The Icelake-Client CPU (removed in 6df39f5e583ca0f67bd934d1327f9ead2e3bd49c)
handled this by modifying the '.notes' section to add the word
'deprecated':
{
.version = 2,
.note = "no TSX, deprecated",
.alias = "Icelake-Client-noTSX",
.props = (PropValue[]) {
{ "hle", "off" },
{ "rtm", "off" },
{ /* end of list */ }
},
},
This relies on the person deprecating the CPU to remember to do this,
and is redundant when this info is already expressed in the
'.deprecation_note' field.
This short series suggests just modifying the '-cpu help'
formatter so that it displays the full deprecation message
eg
$ qemu-system-x86_64 -cpu help:
Available CPUs:
x86 486 (alias configured by machine type) (deprecated: use at least 'Nehalem' / 'Opteron_G4', or 'host' / 'max')
I wonder if this is too verbose, and we should just do a
concise flag like approach, similar to QMP:
$ qemu-system-x86_64 -cpu help:
Available CPUs:
x86 486 (alias configured by machine type) (deprecated)
leaving the full message to be displayed at runtime ? I'm slightly
inclined to the simpler more concise output.
This series touched x86_64, s390x, and aarch64 because that's all I
personally needed from a downstream POV, but any & all of the targets
would benefit from this. They have each implemneted the '-cpu help'
logic independantly though, and unifying that code is not entirely
straightforward.
Daniel P. Berrangé (3):
target/i386: display deprecation note in '-cpu help'
target/s390x: display deprecation note in '-cpu help'
target/arm: display deprecation note in '-cpu help'
target/arm/helper.c | 10 +++++++++-
target/i386/cpu.c | 13 ++++++++++++-
target/s390x/cpu_models.c | 28 +++++++++++++++++++++++-----
3 files changed, 44 insertions(+), 7 deletions(-)
--
2.36.1
next reply other threads:[~2022-07-14 15:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 15:07 Daniel P. Berrangé [this message]
2022-07-14 15:07 ` [PATCH 1/3] target/i386: display deprecation note in '-cpu help' Daniel P. Berrangé
2022-07-15 8:28 ` Cornelia Huck
2022-07-14 15:07 ` [PATCH 2/3] target/s390x: " Daniel P. Berrangé
2022-07-15 8:33 ` Cornelia Huck
2022-07-14 15:07 ` [PATCH 3/3] target/arm: " Daniel P. Berrangé
2022-07-15 8:37 ` Cornelia Huck
2022-07-15 8:45 ` [PATCH 0/3] target: RFC: display deprecation note for " Cornelia Huck
2022-07-18 9:25 ` Thomas Huth
2022-07-18 9:37 ` Cornelia Huck
2022-07-18 9:46 ` Daniel P. Berrangé
2022-07-18 9:58 ` Cornelia Huck
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=20220714150735.1835166-1-berrange@redhat.com \
--to=berrange@redhat.com \
--cc=cohuck@redhat.com \
--cc=david@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=richard.henderson@linaro.org \
--cc=thuth@redhat.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.