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,
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,
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 v7 1/8] machine: Use error handling when CPU type is checked
Date: Wed, 29 Nov 2023 09:47:47 +1100 [thread overview]
Message-ID: <a89a52af-ad01-4a71-a533-fff555c4e938@redhat.com> (raw)
In-Reply-To: <013fb5f5-8281-4f7a-83c8-ac22f845297b@linaro.org>
Hi Phil,
On 11/28/23 20:43, Philippe Mathieu-Daudé wrote:
> On 27/11/23 00:12, Gavin Shan wrote:
>> QEMU will be terminated if the specified CPU type isn't supported
>> in machine_run_board_init(). The list of supported CPU type names
>> is tracked by mc->valid_cpu_types.
>>
>> The error handling can be used to propagate error messages, to be
>> consistent how the errors are handled for other situations in the
>> same function.
>>
>> No functional change intended.
>>
>> Suggested-by: Igor Mammedov <imammedo@redhat.com>
>> Signed-off-by: Gavin Shan <gshan@redhat.com>
>> ---
>> v7: Add 'return' after error_propagate() to avoid calling into
>> mc->init() in the failing case (Marcin)
>> ---
>> hw/core/machine.c | 15 +++++++++------
>> 1 file changed, 9 insertions(+), 6 deletions(-)
>>
>> diff --git a/hw/core/machine.c b/hw/core/machine.c
>> index 0c17398141..b3ef325936 100644
>> --- a/hw/core/machine.c
>> +++ b/hw/core/machine.c
>> @@ -1394,6 +1394,7 @@ void machine_run_board_init(MachineState *machine, const char *mem_path, Error *
>> MachineClass *machine_class = MACHINE_GET_CLASS(machine);
>> ObjectClass *oc = object_class_by_name(machine->cpu_type);
>> CPUClass *cc;
>> + Error *local_err = NULL;
>
> IIUC the big comment in "include/qapi/error.h", since commit ae7c80a7bd
> ("error: New macro ERRP_GUARD()") we want to use the new macro instead.
>
Yeah, there already has a ERRP_GUARD() in machine_run_board_init(). After
rechecking the implementation of ERRP_GUARD(), I found @local_err needs to
be dropped and use @errp below.
>> /* This checkpoint is required by replay to separate prior clock
>> reading from the other reads, because timer polling functions query
>> @@ -1466,15 +1467,17 @@ void machine_run_board_init(MachineState *machine, const char *mem_path, Error *
>> if (!machine_class->valid_cpu_types[i]) {
>> /* The user specified CPU is not valid */
>> - error_report("Invalid CPU type: %s", machine->cpu_type);
>> - error_printf("The valid types are: %s",
>> - machine_class->valid_cpu_types[0]);
>> + error_setg(&local_err, "Invalid CPU type: %s", machine->cpu_type);
>> + error_append_hint(&local_err, "The valid types are: %s",
>> + machine_class->valid_cpu_types[0]);
>> for (i = 1; machine_class->valid_cpu_types[i]; i++) {
>> - error_printf(", %s", machine_class->valid_cpu_types[i]);
>> + error_append_hint(&local_err, ", %s",
>> + machine_class->valid_cpu_types[i]);
>> }
>> - error_printf("\n");
>> + error_append_hint(&local_err, "\n");
>> - exit(1);
>> + error_propagate(errp, local_err);
>> + return;
>> }
>> }
@local_err needs to be replaced with @errp in this chunk of code, as mentioned
above.
Thanks,
Gavin
next prev parent reply other threads:[~2023-11-28 22:48 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 [this message]
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
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=a89a52af-ad01-4a71-a533-fff555c4e938@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).