From: David Gibson <david@gibson.dropbear.id.au>
To: "Cédric Le Goater" <clg@kaod.org>
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 18:32:38 +1000 [thread overview]
Message-ID: <20190722083238.GC25073@umbus.fritz.box> (raw)
In-Reply-To: <215c832d-779c-1597-02af-3a3a52e19f01@kaod.org>
[-- Attachment #1: Type: text/plain, Size: 1864 bytes --]
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.
--
David Gibson | I'll have my music baroque, and my code
david AT gibson.dropbear.id.au | minimalist, thank you. NOT _the_ _other_
| _way_ _around_!
http://www.ozlabs.org/~dgibson
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-07-22 10:57 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 [this message]
2019-07-22 18:24 ` Cédric Le Goater
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=20190722083238.GC25073@umbus.fritz.box \
--to=david@gibson.dropbear.id.au \
--cc=clg@kaod.org \
--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).