From: Michael Ellerman <mpe@ellerman.id.au>
To: Daniel Axtens <dja@axtens.net>,
Russell Currey <ruscur@russell.cc>,
linuxppc-dev@lists.ozlabs.org
Cc: mikey@neuling.org
Subject: Re: [PATCH v2] powerpc: Add POWER9 architected mode to cputable
Date: Fri, 17 Feb 2017 21:11:16 +1100 [thread overview]
Message-ID: <871suxjfej.fsf@concordia.ellerman.id.au> (raw)
In-Reply-To: <878tp58co3.fsf@possimpible.ozlabs.ibm.com>
Daniel Axtens <dja@axtens.net> writes:
> Hi Russell,
>
> This seems to go Power8, Power9, Power7 - is that intentional?
>
> Regards,
> Daniel
>
>> .platform = "power8",
> ...
>> + .platform = "power9",
> ...
>> { /* Power7 */
It's because we have the architected PVRs and the raw ones, and the
ordering is a bit odd:
$ grep -n -e '(architected)' -e '(raw)' arch/powerpc/kernel/cputable.c
323: .cpu_name = "POWER6 (raw)",
343: .cpu_name = "POWER6 (architected)",
356: .cpu_name = "POWER7 (architected)",
374: .cpu_name = "POWER8 (architected)",
392: .cpu_name = "POWER9 (architected)",
411: .cpu_name = "POWER7 (raw)",
431: .cpu_name = "POWER7+ (raw)",
451: .cpu_name = "POWER8E (raw)",
471: .cpu_name = "POWER8NVL (raw)",
491: .cpu_name = "POWER8 (raw)",
511: .cpu_name = "POWER8 (raw)",
531: .cpu_name = "POWER9 (raw)",
550: .cpu_name = "POWER9 (raw)",
But I don't think it matters in practice. The architected entries use a
pvr_mask of 0xffffffff so it has to be an exact match.
cheers
next prev parent reply other threads:[~2017-02-17 10:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 2:01 [PATCH v2] powerpc: Add POWER9 architected mode to cputable Russell Currey
2017-02-17 8:05 ` Daniel Axtens
2017-02-17 10:11 ` Michael Ellerman [this message]
2017-02-17 10:26 ` Michael Ellerman
2017-02-17 12:05 ` Russell Currey
2017-02-17 12:06 ` Russell Currey
2017-02-18 7:54 ` Michael Ellerman
2017-02-19 11:33 ` [v2] " Michael Ellerman
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=871suxjfej.fsf@concordia.ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=dja@axtens.net \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.org \
--cc=ruscur@russell.cc \
/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.