From: Michael Ellerman <mpe@ellerman.id.au>
To: Michael Neuling <mikey@neuling.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Michael Neuling <mikey@neuling.org>,
linuxppc-dev@lists.ozlabs.org,
"Aneesh Kumar K.V" <aneesh.kumar@linux.vnet.ibm.com>
Subject: Re: [v2,3/3] powerpc: Add POWER9 cputable entry
Date: Thu, 25 Feb 2016 01:34:21 +1100 (AEDT) [thread overview]
Message-ID: <20160224143421.C63A914076B@ozlabs.org> (raw)
In-Reply-To: <1455840984-24068-4-git-send-email-mikey@neuling.org>
On Fri, 2016-19-02 at 00:16:24 UTC, 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_300 bit to start hanging new architecture
> features from (in subsequent patches).
> - Advertises new user features bits PPC_FEATURE2_ARCH_3_00 &
> HAS_IEEE128 when on POWER9.
> - Drops CPU_FTR_SUBCORE.
> - Drops PMU code and machine check.
>
> Signed-off-by: Michael Neuling <mikey@neuling.org>
Applied to powerpc next, thanks.
https://git.kernel.org/powerpc/c/c3ab300ea55541014348561e76
cheers
prev parent reply other threads:[~2016-02-24 14:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-19 0:16 [PATCH v2 0/3] powerpc: Add POWER9 cputable entry Michael Neuling
2016-02-19 0:16 ` [PATCH v2 1/3] powerpc/powernv: Create separate subcores CPU feature bit Michael Neuling
2016-02-24 14:34 ` [v2, " Michael Ellerman
2016-02-19 0:16 ` [PATCH v2 2/3] powerpc: Use defines for __init_tlb_power[78] Michael Neuling
2016-02-24 14:34 ` [v2,2/3] " Michael Ellerman
2016-02-19 0:16 ` [PATCH v2 3/3] powerpc: Add POWER9 cputable entry Michael Neuling
2016-02-24 14:34 ` Michael Ellerman [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=20160224143421.C63A914076B@ozlabs.org \
--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).