From: Gavin Shan <gshan@redhat.com>
To: "Philippe Mathieu-Daudé" <philmd@linaro.org>, qemu-arm@nongnu.org
Cc: qemu-devel@nongnu.org, qemu-riscv@nongnu.org,
peter.maydell@linaro.org, imammedo@redhat.com,
b.galvani@gmail.com, strahinja.p.jankovic@gmail.com,
sundeep.lkml@gmail.com, kfting@nuvoton.com, wuhaotsh@google.com,
nieklinnenbank@gmail.com, rad@semihalf.com,
quic_llindhol@quicinc.com, marcin.juszkiewicz@linaro.org,
eduardo@habkost.net, marcel.apfelbaum@gmail.com,
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 v8 3/9] machine: Improve is_cpu_type_supported()
Date: Mon, 4 Dec 2023 09:20:42 +1000 [thread overview]
Message-ID: <fa0e8be7-8f18-4d74-ad5d-6dc44d375d2d@redhat.com> (raw)
In-Reply-To: <83046c42-1df3-499e-b202-b123391d39cb@linaro.org>
Hi Phil
On 12/1/23 20:57, Philippe Mathieu-Daudé wrote:
> On 29/11/23 05:20, Gavin Shan wrote:
>> It's no sense to check the CPU type when mc->valid_cpu_types[0] is
>> NULL.
>
> This case is a programming error, right? We should simply:
>
> assert(!mc->valid_cpu_types || *mc->valid_cpu_types);
>
Yes, assert() should be used instead. I will do this like below:
if (mc->valid_cpu_types && machine->cpu_type) {
assert(mc->valid_cpu_types[1] != NULL);
>> So the check is skipped for this particular case. The constraint
>> has been taken when the error messags are appended.
>>
>> A precise hint for the error message is given when mc->valid_cpu_types[0]
>> is the only valid entry. Besides, enumeration on mc->valid_cpu_types[0]
>> when we have mutiple valid entries there is avoided to increase the code
>> readability, as suggested by Philippe Mathieu-Daudé.
>>
>> Signed-off-by: Gavin Shan <gshan@redhat.com>
>> ---
>> hw/core/machine.c | 18 ++++++++++++------
>> 1 file changed, 12 insertions(+), 6 deletions(-)
>
Thanks,
Gavin
next prev parent reply other threads:[~2023-12-03 23:22 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-29 4:20 [PATCH v8 0/9] Unified CPU type check Gavin Shan
2023-11-29 4:20 ` [PATCH v8 1/9] machine: Use error handling when CPU type is checked Gavin Shan
2023-11-29 8:20 ` Markus Armbruster
2023-12-01 3:33 ` Gavin Shan
2023-11-29 4:20 ` [PATCH v8 2/9] machine: Introduce helper is_cpu_type_supported() Gavin Shan
2023-12-01 10:53 ` Philippe Mathieu-Daudé
2023-12-03 23:13 ` Gavin Shan
2024-01-05 11:10 ` Philippe Mathieu-Daudé
2023-11-29 4:20 ` [PATCH v8 3/9] machine: Improve is_cpu_type_supported() Gavin Shan
2023-12-01 10:57 ` Philippe Mathieu-Daudé
2023-12-03 23:20 ` Gavin Shan [this message]
2023-12-03 23:30 ` Gavin Shan
2023-11-29 4:20 ` [PATCH v8 4/9] machine: Print CPU model name instead of CPU type Gavin Shan
2023-12-01 10:58 ` Philippe Mathieu-Daudé
2023-11-29 4:20 ` [PATCH v8 5/9] hw/arm/virt: Hide host CPU model for tcg Gavin Shan
2023-11-29 4:20 ` [PATCH v8 6/9] hw/arm/virt: Check CPU type in machine_run_board_init() Gavin Shan
2023-11-29 4:20 ` [PATCH v8 7/9] hw/arm/sbsa-ref: " Gavin Shan
2023-11-29 4:20 ` [PATCH v8 8/9] hw/arm: " Gavin Shan
2023-11-29 4:20 ` [PATCH v8 9/9] hw/riscv/shakti_c: " Gavin Shan
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=fa0e8be7-8f18-4d74-ad5d-6dc44d375d2d@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=shan.gavin@gmail.com \
--cc=strahinja.p.jankovic@gmail.com \
--cc=sundeep.lkml@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).