From: "Cédric Le Goater" <clg@kaod.org>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: qemu-ppc@nongnu.org, Joel Stanley <joel@jms.id.au>,
qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] ppc/pnv: update skiboot to v6.4
Date: Mon, 22 Jul 2019 20:24:53 +0200 [thread overview]
Message-ID: <358f8d9e-4de4-5fcf-3d82-4fce9126b7a4@kaod.org> (raw)
In-Reply-To: <20190722083238.GC25073@umbus.fritz.box>
On 22/07/2019 10:32, David Gibson wrote:
> On Thu, Jul 18, 2019 at 03:03:09PM +0200, Cédric Le Goater wrote:
>> On 18/07/2019 08:16, David Gibson wrote:
>>> On Thu, Jul 18, 2019 at 03:12:17PM +0930, Joel Stanley wrote:
>>>> Currently we fail to boot a qemu powernv machine with a Power9
>>>> processor:
>>>>
>>>> PLAT: Detected generic platform
>>>> PLAT: Detected BMC platform generic
>>>> CPU: All 1 processors called in...
>>>> CHIPTOD: Unknown TOD type !
>>>> CHIPTOD: Failed ChipTOD detection !
>>>> Aborting!
>>>>
>>>> With v6.4 we can boot both a Power8 and Power9 powernv machine.
>>>>
>>>> Built from submodule with powerpc64le-linux-gnu-gcc (Debian 8.3.0-2).
>>>>
>>>> Signed-off-by: Joel Stanley <joel@jms.id.au>
>>> Applied to ppc-for-4.2, thanks.
>>>
>>> If you could add both POWER8 and POWER9 smoke tests to
>>> boot-serial-test that would be even better.
>>
>> There is one for POWER8 and adding an extra for POWER9 results
>> in a test conflict. So I came up with the patch below. Would that
>> be OK ?
>
> Ugh. This name mangling is pretty ugly. It would be neater to extend
> the table format to have cpu explicitly and base the test names on
> that, rather than special casing powernv.
>
> But...
>
> It occurs to me the reason we're hitting this is that for the other
> systems represented here, the exact cpu model is really just a
> detail. It's not for us, because the whole system is substantially
> different for the two cpus.
>
> Which says to me that tbe POWER8 and POWER9 systems should really be
> different machine types, not lumped together in "powernv" which then
> has a heap of conditionals on the cpu family. If we do that, the
> problem here goes away.
Yes. I just sent a patch for it.
Thanks,
C.
prev parent reply other threads:[~2019-07-22 18:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190718054218.9581-1-joel@jms.id.au>
[not found] ` <20190718061628.GM8468@umbus.fritz.box>
2019-07-18 13:03 ` [Qemu-devel] [PATCH] ppc/pnv: update skiboot to v6.4 Cédric Le Goater
2019-07-22 8:32 ` David Gibson
2019-07-22 18:24 ` Cédric Le Goater [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=358f8d9e-4de4-5fcf-3d82-4fce9126b7a4@kaod.org \
--to=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=joel@jms.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 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).