qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Gavin Shan <gshan@redhat.com>
To: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>, qemu-arm@nongnu.org
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
	peter.maydell@linaro.org, imammedo@redhat.com,
	richard.henderson@linaro.org, quic_llindhol@quicinc.com,
	b.galvani@gmail.com, strahinja.p.jankovic@gmail.com,
	kfting@nuvoton.com, wuhaotsh@google.com,
	nieklinnenbank@gmail.com, rad@semihalf.com, eduardo@habkost.net,
	marcel.apfelbaum@gmail.com, philmd@linaro.org,
	wangyanan55@huawei.com, vijai@behindbytes.com,
	palmer@dabbelt.com, alistair.francis@wdc.com,
	bin.meng@windriver.com, liwei1518@gmail.com,
	dbarboza@ventanamicro.com, zhiwei_liu@linux.alibaba.com,
	shan.gavin@gmail.com
Subject: Re: [PATCH v7 0/8] Unified CPU type check
Date: Mon, 27 Nov 2023 21:15:49 +1100	[thread overview]
Message-ID: <1a4e1fa1-ee5f-457e-86e3-2dd2a27500e5@redhat.com> (raw)
In-Reply-To: <35c87631-062c-43e8-bf46-67aa3cef5b30@linaro.org>


On 11/27/23 21:10, Marcin Juszkiewicz wrote:
> W dniu 27.11.2023 o 00:12, Gavin Shan pisze:
>> After the series is applied:
>>
>>    [gshan@gshan q]$ ./build/qemu-system-aarch64 -M virt -cpu cortex-a8
>>    qemu-system-aarch64: Invalid CPU type: cortex-a8
>>    The valid types are: cortex-a7, cortex-a15, cortex-a35, cortex-a55,     \
>>                         cortex-a72, cortex-a76, cortex-a710, a64fx,        \
>>                         neoverse-n1, neoverse-v1, neoverse-n2, cortex-a53, \
>>                         cortex-a57, max
> 
> Can this list have some better order? A35, A53, A55, A57, A72 feels better than current one.
> 

Definitely a good idea. I think this series is about to be queued,
let me send one additional patch to do so after this series is
merged.

Thanks,
Gavin



      reply	other threads:[~2023-11-27 10:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-26 23:12 [PATCH v7 0/8] Unified CPU type check Gavin Shan
2023-11-26 23:12 ` [PATCH v7 1/8] machine: Use error handling when CPU type is checked Gavin Shan
2023-11-28  9:43   ` Philippe Mathieu-Daudé
2023-11-28 22:47     ` Gavin Shan
2023-11-26 23:12 ` [PATCH v7 2/8] machine: Introduce helper is_cpu_type_supported() Gavin Shan
2023-11-28  9:38   ` Philippe Mathieu-Daudé
2023-11-28 22:55     ` Gavin Shan
2023-11-26 23:12 ` [PATCH v7 3/8] machine: Print CPU model name instead of CPU type Gavin Shan
2023-11-28  9:55   ` Philippe Mathieu-Daudé
2023-11-29  3:53     ` Gavin Shan
2023-11-26 23:12 ` [PATCH v7 4/8] hw/arm/virt: Hide host CPU model for tcg Gavin Shan
2023-11-28  9:29   ` Philippe Mathieu-Daudé
2023-11-26 23:12 ` [PATCH v7 5/8] hw/arm/virt: Check CPU type in machine_run_board_init() Gavin Shan
2023-11-27 10:13   ` Marcin Juszkiewicz
2023-11-27 10:42     ` Gavin Shan
2023-11-26 23:12 ` [PATCH v7 6/8] hw/arm/sbsa-ref: " Gavin Shan
2023-11-26 23:12 ` [PATCH v7 7/8] hw/arm: " Gavin Shan
2023-11-28  9:31   ` Philippe Mathieu-Daudé
2023-11-26 23:12 ` [PATCH v7 8/8] hw/riscv/shakti_c: " Gavin Shan
2023-11-27 10:10 ` [PATCH v7 0/8] Unified CPU type check Marcin Juszkiewicz
2023-11-27 10:15   ` Gavin Shan [this message]

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=1a4e1fa1-ee5f-457e-86e3-2dd2a27500e5@redhat.com \
    --to=gshan@redhat.com \
    --cc=alistair.francis@wdc.com \
    --cc=b.galvani@gmail.com \
    --cc=bin.meng@windriver.com \
    --cc=dbarboza@ventanamicro.com \
    --cc=eduardo@habkost.net \
    --cc=imammedo@redhat.com \
    --cc=kfting@nuvoton.com \
    --cc=liwei1518@gmail.com \
    --cc=marcel.apfelbaum@gmail.com \
    --cc=marcin.juszkiewicz@linaro.org \
    --cc=nieklinnenbank@gmail.com \
    --cc=palmer@dabbelt.com \
    --cc=peter.maydell@linaro.org \
    --cc=philmd@linaro.org \
    --cc=qemu-arm@nongnu.org \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-riscv@nongnu.org \
    --cc=quic_llindhol@quicinc.com \
    --cc=rad@semihalf.com \
    --cc=richard.henderson@linaro.org \
    --cc=shan.gavin@gmail.com \
    --cc=strahinja.p.jankovic@gmail.com \
    --cc=vijai@behindbytes.com \
    --cc=wangyanan55@huawei.com \
    --cc=wuhaotsh@google.com \
    --cc=zhiwei_liu@linux.alibaba.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 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).