From: Thomas Huth <thuth@redhat.com>
To: Peter Maydell <peter.maydell@linaro.org>,
qemu-arm@nongnu.org, qemu-devel@nongnu.org
Cc: "Philippe Mathieu-Daudé" <f4bug@amsat.org>,
"Pekka Enberg" <penberg@iki.fi>,
"Andrew Baumann" <Andrew.Baumann@microsoft.com>,
patches@linaro.org
Subject: Re: [Qemu-devel] [PATCH 6/9] hw/arm/bcm2836: Create proper bcm2837 device
Date: Mon, 18 Jun 2018 18:02:08 +0200 [thread overview]
Message-ID: <9d6c5256-289c-6e64-c141-d5ff2f9f121c@redhat.com> (raw)
In-Reply-To: <20180313153458.26822-7-peter.maydell@linaro.org>
On 13.03.2018 16:34, Peter Maydell wrote:
> The bcm2837 is pretty similar to the bcm2836, but it does have
> some differences. Notably, the MPIDR affinity aff1 values it
> sets for the CPUs are 0x0, rather than the 0xf that the bcm2836
> uses, and if this is wrong Linux will not boot.
>
> Rather than trying to have one device with properties that
> configure it differently for the two cases, create two
> separate QOM devices for the two SoCs. We use the same approach
> as hw/arm/aspeed_soc.c and share code and have a data table
> that might differ per-SoC. For the moment the two types don't
> actually have different behaviour.
>
> Signed-off-by: Peter Maydell <peter.maydell@linaro.org>
> ---
> include/hw/arm/bcm2836.h | 19 +++++++++++++++++++
> hw/arm/bcm2836.c | 37 ++++++++++++++++++++++++++++++++-----
> hw/arm/raspi.c | 3 ++-
> 3 files changed, 53 insertions(+), 6 deletions(-)
Hi Peter,
if I've bisected it right, this patch introduced a new way to crash QEMU:
$ aarch64-softmmu/qemu-system-aarch64 -M integratorcp,accel=qtest \
-nographic
QEMU 2.11.50 monitor - type 'help' for more information
(qemu) device_add bcm2837
Device 'bcm2837' can not be hotplugged on this machine
(qemu) device_add corgi-ssp
Segmentation fault (core dumped)
Not sure why this is happening, though, I can't see anything obvious
wrong with your patch.
Thomas
> diff --git a/include/hw/arm/bcm2836.h b/include/hw/arm/bcm2836.h
> index 9a10a76631..93248399ba 100644
> --- a/include/hw/arm/bcm2836.h
> +++ b/include/hw/arm/bcm2836.h
> @@ -20,6 +20,13 @@
>
> #define BCM283X_NCPUS 4
>
> +/* These type names are for specific SoCs; other than instantiating
> + * them, code using these devices should always handle them via the
> + * BCM283x base class, so they have no BCM2836(obj) etc macros.
> + */
> +#define TYPE_BCM2836 "bcm2836"
> +#define TYPE_BCM2837 "bcm2837"
> +
> typedef struct BCM283XState {
> /*< private >*/
> DeviceState parent_obj;
> @@ -33,4 +40,16 @@ typedef struct BCM283XState {
> BCM2835PeripheralState peripherals;
> } BCM283XState;
>
> +typedef struct BCM283XInfo BCM283XInfo;
> +
> +typedef struct BCM283XClass {
> + DeviceClass parent_class;
> + const BCM283XInfo *info;
> +} BCM283XClass;
> +
> +#define BCM283X_CLASS(klass) \
> + OBJECT_CLASS_CHECK(BCM283XClass, (klass), TYPE_BCM283X)
> +#define BCM283X_GET_CLASS(obj) \
> + OBJECT_GET_CLASS(BCM283XClass, (obj), TYPE_BCM283X)
> +
> #endif /* BCM2836_H */
> diff --git a/hw/arm/bcm2836.c b/hw/arm/bcm2836.c
> index 1d1908654b..07d2705f96 100644
> --- a/hw/arm/bcm2836.c
> +++ b/hw/arm/bcm2836.c
> @@ -23,6 +23,19 @@
> /* "QA7" (Pi2) interrupt controller and mailboxes etc. */
> #define BCM2836_CONTROL_BASE 0x40000000
>
> +struct BCM283XInfo {
> + const char *name;
> +};
> +
> +static const BCM283XInfo bcm283x_socs[] = {
> + {
> + .name = TYPE_BCM2836,
> + },
> + {
> + .name = TYPE_BCM2837,
> + },
> +};
> +
> static void bcm2836_init(Object *obj)
> {
> BCM283XState *s = BCM283X(obj);
> @@ -156,25 +169,39 @@ static Property bcm2836_props[] = {
> DEFINE_PROP_END_OF_LIST()
> };
>
> -static void bcm2836_class_init(ObjectClass *oc, void *data)
> +static void bcm283x_class_init(ObjectClass *oc, void *data)
> {
> DeviceClass *dc = DEVICE_CLASS(oc);
> + BCM283XClass *bc = BCM283X_CLASS(oc);
>
> - dc->props = bcm2836_props;
> + bc->info = data;
> dc->realize = bcm2836_realize;
> + dc->props = bcm2836_props;
> }
>
> -static const TypeInfo bcm2836_type_info = {
> +static const TypeInfo bcm283x_type_info = {
> .name = TYPE_BCM283X,
> .parent = TYPE_DEVICE,
> .instance_size = sizeof(BCM283XState),
> .instance_init = bcm2836_init,
> - .class_init = bcm2836_class_init,
> + .class_size = sizeof(BCM283XClass),
> + .abstract = true,
> };
>
> static void bcm2836_register_types(void)
> {
> - type_register_static(&bcm2836_type_info);
> + int i;
> +
> + type_register_static(&bcm283x_type_info);
> + for (i = 0; i < ARRAY_SIZE(bcm283x_socs); i++) {
> + TypeInfo ti = {
> + .name = bcm283x_socs[i].name,
> + .parent = TYPE_BCM283X,
> + .class_init = bcm283x_class_init,
> + .class_data = (void *) &bcm283x_socs[i],
> + };
> + type_register(&ti);
> + }
> }
>
> type_init(bcm2836_register_types)
> diff --git a/hw/arm/raspi.c b/hw/arm/raspi.c
> index 58c6e80a17..f588720138 100644
> --- a/hw/arm/raspi.c
> +++ b/hw/arm/raspi.c
> @@ -136,7 +136,8 @@ static void raspi_init(MachineState *machine, int version)
> BusState *bus;
> DeviceState *carddev;
>
> - object_initialize(&s->soc, sizeof(s->soc), TYPE_BCM283X);
> + object_initialize(&s->soc, sizeof(s->soc),
> + version == 3 ? TYPE_BCM2837 : TYPE_BCM2836);
> object_property_add_child(OBJECT(machine), "soc", OBJECT(&s->soc),
> &error_abort);
>
>
next prev parent reply other threads:[~2018-06-18 16:02 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-13 15:34 [Qemu-devel] [PATCH 0/9] raspi3: various fixes for Linux booting Peter Maydell
2018-03-13 15:34 ` [Qemu-devel] [PATCH 1/9] hw/arm/raspi: Don't do board-setup or secure-boot for raspi3 Peter Maydell
2018-03-13 16:34 ` Andrew Baumann
2018-03-13 23:20 ` [Qemu-devel] [Qemu-arm] " Philippe Mathieu-Daudé
2018-03-13 15:34 ` [Qemu-devel] [PATCH 2/9] hw/arm/boot: assert that secure_boot and secure_board_setup are false for AArch64 Peter Maydell
2018-03-13 23:23 ` Philippe Mathieu-Daudé
2018-03-13 15:34 ` [Qemu-devel] [PATCH 3/9] hw/arm/boot: If booting a kernel in EL2, set SCR_EL3.HCE Peter Maydell
2018-03-13 15:34 ` [Qemu-devel] [PATCH 4/9] hw/arm/bcm2386: Fix parent type of bcm2386 Peter Maydell
2018-03-13 16:40 ` Andrew Baumann
2018-03-13 23:04 ` Philippe Mathieu-Daudé
2018-03-13 15:34 ` [Qemu-devel] [PATCH 5/9] hw/arm/bcm2836: Rename bcm2836 type/struct to bcm283x Peter Maydell
2018-03-13 16:43 ` Andrew Baumann
2018-03-13 22:58 ` Philippe Mathieu-Daudé
2018-03-13 15:34 ` [Qemu-devel] [PATCH 6/9] hw/arm/bcm2836: Create proper bcm2837 device Peter Maydell
2018-03-13 16:47 ` Andrew Baumann
2018-03-13 23:00 ` Philippe Mathieu-Daudé
2018-06-18 16:02 ` Thomas Huth [this message]
2018-03-13 15:34 ` [Qemu-devel] [PATCH 7/9] hw/arm/bcm2836: Use correct affinity values for BCM2837 Peter Maydell
2018-03-13 16:48 ` Andrew Baumann
2018-03-13 17:06 ` Peter Maydell
2018-03-15 12:10 ` Philippe Mathieu-Daudé
2018-03-13 15:34 ` [Qemu-devel] [PATCH 8/9] hw/arm/bcm2836: Hardcode correct CPU type Peter Maydell
2018-03-13 16:55 ` Andrew Baumann
2018-03-13 17:09 ` Peter Maydell
2018-03-13 23:16 ` Philippe Mathieu-Daudé
2018-03-19 10:58 ` Peter Maydell
2018-03-13 23:16 ` Philippe Mathieu-Daudé
2018-03-15 17:13 ` Peter Maydell
2018-03-19 14:40 ` Igor Mammedov
2018-03-19 18:25 ` Peter Maydell
2018-03-13 23:06 ` Philippe Mathieu-Daudé
2018-03-19 11:57 ` [Qemu-devel] [Qemu-arm] " Peter Maydell
2018-03-13 15:34 ` [Qemu-devel] [PATCH 9/9] hw/arm/raspi: Provide spin-loop code for AArch64 CPUs Peter Maydell
2018-03-15 12:31 ` Philippe Mathieu-Daudé
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=9d6c5256-289c-6e64-c141-d5ff2f9f121c@redhat.com \
--to=thuth@redhat.com \
--cc=Andrew.Baumann@microsoft.com \
--cc=f4bug@amsat.org \
--cc=patches@linaro.org \
--cc=penberg@iki.fi \
--cc=peter.maydell@linaro.org \
--cc=qemu-arm@nongnu.org \
--cc=qemu-devel@nongnu.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).