From: Michael Ellerman <mpe@ellerman.id.au>
To: Michael Neuling <mikey@neuling.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: linuxppc-dev@lists.ozlabs.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [PATCH 2/2] powerpc: Add POWER9 cputable entry
Date: Thu, 18 Feb 2016 21:37:07 +1100 [thread overview]
Message-ID: <1455791827.5284.7.camel@ellerman.id.au> (raw)
In-Reply-To: <1455766350.22981.15.camel@neuling.org>
On Thu, 2016-02-18 at 14:32 +1100, Michael Neuling wrote:
> On Wed, 2016-02-17 at 22:09 +1100, Michael Ellerman wrote:
> > On Wed, 2016-02-17 at 16:07 +1100, Michael Neuling wrote:
> >
> > > Add a cputable entry for POWER9. More code is required to actually
> > > boot and run on a POWER9 but this gets the base piece in which we
> > > can
> > > start building on.
> > >
> > > Copies over from POWER8 except for:
> > > - Adds a new CPU_FTR_ARCH_30 bit to start hanging new architecture
> >
> > ARCH thirty?
> >
> > Would CPU_FTR_ARCH_3 read better?
> >
> > Or CPU_FTR_ARCH_3_00 ?
>
> The actual architecture book used to say 2.07 but now says just 3.0.
> Hence why I picked 30 vs 207.
Yeah I get the logic.
> That being said, I don't really care what we call it.
I like CPU_FTR_ARCH_3.
cheers
next prev parent reply other threads:[~2016-02-18 10:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-17 5:07 [PATCH 1/2] powerpc/powernv: Create separate subcores CPU feature bit Michael Neuling
2016-02-17 5:07 ` [PATCH 2/2] powerpc: Add POWER9 cputable entry Michael Neuling
2016-02-17 6:03 ` Madhavan Srinivasan
2016-02-17 9:10 ` Michael Neuling
2016-02-17 11:09 ` Michael Ellerman
2016-02-17 12:28 ` oliver
2016-02-17 12:49 ` Michael Ellerman
2016-02-18 3:32 ` Michael Neuling
2016-02-18 10:37 ` Michael Ellerman [this message]
2016-02-17 14:59 ` [PATCH 1/2] powerpc/powernv: Create separate subcores CPU feature bit Aneesh Kumar K.V
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=1455791827.5284.7.camel@ellerman.id.au \
--to=mpe@ellerman.id.au \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mikey@neuling.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).