From: Thomas Huth <thuth@redhat.com>
To: "Cédric Le Goater" <clg@kaod.org>,
"QEMU Developers" <qemu-devel@nongnu.org>,
"qemu-ppc@nongnu.org" <qemu-ppc@nongnu.org>
Cc: David Gibson <david@gibson.dropbear.id.au>
Subject: Re: Assertion triggers with power8e_v2.1-powernv-cpu-core
Date: Wed, 29 Jan 2020 11:48:12 +0100 [thread overview]
Message-ID: <2a37c985-2ada-e64d-5f4e-fb158e372af5@redhat.com> (raw)
In-Reply-To: <db907c1e-9a67-0eeb-ef18-c710e68cd311@kaod.org>
On 29/01/2020 11.39, Cédric Le Goater wrote:
> On 1/29/20 11:31 AM, Thomas Huth wrote:
>> FYI, scripts/device-crash-test reported an assertion, triggerable like this:
>>
>> $ qemu-system-ppc64 -machine ppce500 -device power8e_v2.1-powernv-cpu-core
>> qemu-system-ppc64: hw/ppc/pnv_core.c:221: pnv_core_realize: Assertion
>> `pc->chip' failed.
>> Aborted (core dumped)
>>
>> Of course using that CPU is not possible on ppce500, but there should be
>> a proper error message instead of that assertion.
>>
>> Does anybody have an idea what's the best place to fix this issue?
>
> The cores should be instantiated by a PowerNV chip. So may be we
> should fix this issue with :
>
> @@ -325,6 +325,7 @@ static void pnv_core_class_init(ObjectCl
> dc->realize = pnv_core_realize;
> dc->unrealize = pnv_core_unrealize;
> device_class_set_props(dc, pnv_core_properties);
> + dc->user_creatable = false;
> }
>
> #define DEFINE_PNV_CORE_TYPE(family, cpu_model) \
>
>
> I think that most of the PowerNV devices are not user creatable.
Right, there are also aborts with: pnv-lpc, pnv-homer, pnv-occ, ...
Do you have some spare time for a patch?
Thomas
prev parent reply other threads:[~2020-01-29 10:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-29 10:31 Assertion triggers with power8e_v2.1-powernv-cpu-core Thomas Huth
2020-01-29 10:39 ` Cédric Le Goater
2020-01-29 10:48 ` Thomas Huth [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=2a37c985-2ada-e64d-5f4e-fb158e372af5@redhat.com \
--to=thuth@redhat.com \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.