From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: qemu-devel@nongnu.org
Cc: qemu-arm@nongnu.org,
"Arnaud Minier" <arnaud.minier@telecom-paris.fr>,
"Inès Varhol" <ines.varhol@telecom-paris.fr>,
"Tyrone Ting" <kfting@nuvoton.com>,
"Subbaraya Sundeep" <sbhatta@marvell.com>,
"Hao Wu" <wuhaotsh@google.com>, "Felipe Balbi" <balbi@kernel.org>,
"Gavin Shan" <gshan@redhat.com>,
"Igor Mammedov" <imammedo@redhat.com>,
"Subbaraya Sundeep" <sundeep.lkml@gmail.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
"Eduardo Habkost" <eduardo@habkost.net>,
"Alistair Francis" <alistair@alistair23.me>,
"Alexandre Iooss" <erdnaxe@crans.org>
Subject: Re: [PATCH-for-8.2? 1/6] hw/arm/stm32f405: Report error when incorrect CPU is used
Date: Thu, 16 Nov 2023 08:23:19 +0100 [thread overview]
Message-ID: <1f657e11-909f-433a-8642-3a0176019b4a@linaro.org> (raw)
In-Reply-To: <20231115232154.4515-2-philmd@linaro.org>
On 16/11/23 00:21, Philippe Mathieu-Daudé wrote:
> Both 'netduinoplus2' and 'olimex-stm32-h405' machines ignore the
> CPU type requested by the command line. This might confuse users,
> since the following will create a machine with a Cortex-M4 CPU:
>
> $ qemu-system-aarch64 -M netduinoplus2 -cpu cortex-r5f
>
> Set the MachineClass::valid_cpu_types field (introduced in commit
> c9cf636d48 "machine: Add a valid_cpu_types property").
> Remove the now unused MachineClass::default_cpu_type field.
>
> We now get:
>
> $ qemu-system-aarch64 -M netduinoplus2 -cpu cortex-r5f
> qemu-system-aarch64: Invalid CPU type: cortex-r5f-arm-cpu
> The valid types are: cortex-m4-arm-cpu
>
> Since the SoC family can only use Cortex-M4 CPUs, hard-code the
> CPU type name at the SoC level, removing the QOM property
> entirely.
>
> Signed-off-by: Philippe Mathieu-Daudé <philmd@linaro.org>
> ---
> include/hw/arm/stm32f405_soc.h | 4 ----
> hw/arm/netduinoplus2.c | 7 ++++++-
> hw/arm/olimex-stm32-h405.c | 8 ++++++--
> hw/arm/stm32f405_soc.c | 8 +-------
> 4 files changed, 13 insertions(+), 14 deletions(-)
> diff --git a/hw/arm/olimex-stm32-h405.c b/hw/arm/olimex-stm32-h405.c
> index 3aa61c91b7..694b1dd6ed 100644
> --- a/hw/arm/olimex-stm32-h405.c
> +++ b/hw/arm/olimex-stm32-h405.c
> @@ -47,7 +47,6 @@ static void olimex_stm32_h405_init(MachineState *machine)
> clock_set_hz(sysclk, SYSCLK_FRQ);
>
> dev = qdev_new(TYPE_STM32F405_SOC);
> - qdev_prop_set_string(dev, "cpu-type", ARM_CPU_TYPE_NAME("cortex-m4"));
> qdev_connect_clock_in(dev, "sysclk", sysclk);
> sysbus_realize_and_unref(SYS_BUS_DEVICE(dev), &error_fatal);
>
> @@ -58,9 +57,14 @@ static void olimex_stm32_h405_init(MachineState *machine)
>
> static void olimex_stm32_h405_machine_init(MachineClass *mc)
> {
> + static const char *machine_valid_cpu_types[] = {
const char * const
(in all this series).
> + ARM_CPU_TYPE_NAME("cortex-m4"),
> + NULL
> + };
> +
> mc->desc = "Olimex STM32-H405 (Cortex-M4)";
> mc->init = olimex_stm32_h405_init;
> - mc->default_cpu_type = ARM_CPU_TYPE_NAME("cortex-m4");
> + mc->valid_cpu_types = machine_valid_cpu_types;
>
> /* SRAM pre-allocated as part of the SoC instantiation */
> mc->default_ram_size = 0;
next prev parent reply other threads:[~2023-11-16 7:24 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-15 23:21 [PATCH-for-8.2? 0/6] hw/arm/stm32xxx: Report error when incorrect CPU is used Philippe Mathieu-Daudé
2023-11-15 23:21 ` [PATCH-for-8.2? 1/6] hw/arm/stm32f405: " Philippe Mathieu-Daudé
2023-11-16 7:23 ` Philippe Mathieu-Daudé [this message]
2023-11-15 23:21 ` [PATCH-for-8.2? 2/6] hw/arm/stm32f205: " Philippe Mathieu-Daudé
2023-11-15 23:21 ` [PATCH-for-8.2? 3/6] hw/arm/stm32f100: " Philippe Mathieu-Daudé
2023-11-16 7:25 ` Philippe Mathieu-Daudé
2023-11-15 23:21 ` [PATCH-for-9.0 4/6] hw/arm/msf2: Simplify setting MachineClass::valid_cpu_types[] Philippe Mathieu-Daudé
2023-11-15 23:21 ` [PATCH-for-9.0 5/6] hw/arm/npcm7xx_boards: " Philippe Mathieu-Daudé
2023-11-15 23:21 ` [PATCH-for-9.0 6/6] hw/arm/musca: " Philippe Mathieu-Daudé
2023-11-16 16:46 ` [PATCH-for-8.2? 0/6] hw/arm/stm32xxx: Report error when incorrect CPU is used Richard Henderson
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=1f657e11-909f-433a-8642-3a0176019b4a@linaro.org \
--to=philmd@linaro.org \
--cc=alistair@alistair23.me \
--cc=arnaud.minier@telecom-paris.fr \
--cc=balbi@kernel.org \
--cc=eduardo@habkost.net \
--cc=erdnaxe@crans.org \
--cc=gshan@redhat.com \
--cc=imammedo@redhat.com \
--cc=ines.varhol@telecom-paris.fr \
--cc=kfting@nuvoton.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.org \
--cc=sbhatta@marvell.com \
--cc=sundeep.lkml@gmail.com \
--cc=wuhaotsh@google.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).