From: Thomas Huth <thuth@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: qemu-devel@nongnu.org, Paolo Bonzini <pbonzini@redhat.com>,
qemu-ppc@nongnu.org, qemu-s390x@nongnu.org,
Nicholas Piggin <npiggin@gmail.com>,
Daniel Henrique Barboza <danielhb413@gmail.com>,
David Hildenbrand <david@redhat.com>,
Richard Henderson <richard.henderson@linaro.org>,
qemu-trivial@nongnu.org
Subject: Re: [PATCH 0/3] Remove useless architecture prefix from the CPU list
Date: Mon, 22 Apr 2024 10:22:04 +0200 [thread overview]
Message-ID: <d2786e99-ae33-43a0-8040-8a218bb485f1@redhat.com> (raw)
In-Reply-To: <ZiYZyOqeM2tYPcCs@redhat.com>
On 22/04/2024 10.03, Daniel P. Berrangé wrote:
> On Sat, Apr 20, 2024 at 07:46:03AM +0200, Thomas Huth wrote:
>> Printing an architecture prefix in front of each CPU name is not helpful
>> at all: It is confusing for the users since they don't know whether they
>> have to specify these letters for the "-cpu" parameter, too, and it also
>> takes some precious space in the dense output of the CPU entries. Let's
>> simply remove those now.
>
> Could it be said that this arch prefix is about to finally become useful
> with Philippe's patches to add a 'qemu-system-any' command covering
> multiple arches ?
I don't think so: In that case we'd rather print it once at the beginning of
a list ("Available x86 CPUs:") instead of printing it in each and every line.
Thomas
next prev parent reply other threads:[~2024-04-22 8:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-20 5:46 [PATCH 0/3] Remove useless architecture prefix from the CPU list Thomas Huth
2024-04-20 5:46 ` [PATCH 1/3] target/i386/cpu: Remove "x86" " Thomas Huth
2024-04-20 5:46 ` [PATCH 2/3] target/s390x/cpu_models: Rework the output of "-cpu help" Thomas Huth
2024-04-20 5:46 ` [PATCH 3/3] target/ppc/cpu_init: Remove "PowerPC" prefix from the CPU list Thomas Huth
2024-04-20 14:40 ` [PATCH 0/3] Remove useless architecture " David Hildenbrand
2024-04-20 16:26 ` Richard Henderson
2024-04-20 16:53 ` Michael Tokarev
2024-04-22 8:03 ` Daniel P. Berrangé
2024-04-22 8:22 ` Thomas Huth [this message]
2024-04-29 10:26 ` Philippe Mathieu-Daudé
2024-04-26 9:13 ` Mario Casquero
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=d2786e99-ae33-43a0-8040-8a218bb485f1@redhat.com \
--to=thuth@redhat.com \
--cc=berrange@redhat.com \
--cc=danielhb413@gmail.com \
--cc=david@redhat.com \
--cc=npiggin@gmail.com \
--cc=pbonzini@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=qemu-s390x@nongnu.org \
--cc=qemu-trivial@nongnu.org \
--cc=richard.henderson@linaro.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).