From: Cornelia Huck <cohuck@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>, qemu-devel@nongnu.org
Cc: qemu-s390x@nongnu.org, "Thomas Huth" <thuth@redhat.com>,
qemu-arm@nongnu.org, "David Hildenbrand" <david@redhat.com>,
"Richard Henderson" <richard.henderson@linaro.org>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Daniel P. Berrangé" <berrange@redhat.com>
Subject: Re: [PATCH 1/3] target/i386: display deprecation note in '-cpu help'
Date: Fri, 15 Jul 2022 10:28:35 +0200 [thread overview]
Message-ID: <87y1wu3hl8.fsf@redhat.com> (raw)
In-Reply-To: <20220714150735.1835166-2-berrange@redhat.com>
On Thu, Jul 14 2022, Daniel P. Berrangé <berrange@redhat.com> wrote:
> The deprecation notes are currently only displayed at runtime when the
> user activates a CPU. The QMP query displays a simple flag for
> deprecation, while '-cpu help' displays nothing unless the deprecation
> info is duplicated into the 'notes' field.
>
> This changes the code so that deprecation notes are explicitly shown
> in '-cpu help', to assist the user in deciding what to use.
>
> Signed-off-by: Daniel P. Berrangé <berrange@redhat.com>
> ---
> target/i386/cpu.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
Reviewed-by: Cornelia Huck <cohuck@redhat.com>
next prev parent reply other threads:[~2022-07-15 8:29 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-14 15:07 [PATCH 0/3] target: RFC: display deprecation note for '-cpu help' Daniel P. Berrangé
2022-07-14 15:07 ` [PATCH 1/3] target/i386: display deprecation note in " Daniel P. Berrangé
2022-07-15 8:28 ` Cornelia Huck [this message]
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=87y1wu3hl8.fsf@redhat.com \
--to=cohuck@redhat.com \
--cc=berrange@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.