From: Greg Kurz <groug@kaod.org>
To: Thomas Huth <thuth@redhat.com>
Cc: "Laurent Vivier" <lvivier@redhat.com>,
"David Gibson" <david@gibson.dropbear.id.au>,
"Suraj Singh" <sursingh@redhat.com>,
joserz@linux.vnet.ibm.com, qemu-devel@nongnu.org,
qemu-ppc@nongnu.org, "Cédric Le Goater" <clg@kaod.org>,
"Sam Bobroff" <sbobroff@redhat.com>
Subject: Re: [Qemu-devel] [Qemu-ppc] [RFC v3 1/2] target/ppc/cpu-models: set POWER9_v1.0 as POWER9 DD1
Date: Tue, 4 Jul 2017 10:51:46 +0200 [thread overview]
Message-ID: <20170704105146.6ef17b9f@bahia.lan> (raw)
In-Reply-To: <b11aa61c-ff73-3568-f924-e10828c0e92c@redhat.com>
[-- Attachment #1: Type: text/plain, Size: 1694 bytes --]
On Tue, 4 Jul 2017 09:42:33 +0200
Thomas Huth <thuth@redhat.com> wrote:
> On 03.07.2017 15:14, Laurent Vivier wrote:
> > CPU_POWERPC_POWER9_DD1 is 0x004E0100, so this is the POWER9 v1.0.
> >
> > When we run qemu on a POWER9 DD1 host, we must use either
> > "-cpu host" or "-cpu POWER9", but in the latter case it fails with
> >
> > Unable to find sPAPR CPU Core definition
> >
> > because POWER9 DD1 doesn't appear in the list of known CPUs.
> >
> > This patch fixes this by defining POWER9_v1.0 with POWER9 DD1
> > PVR instead of CPU_POWERPC_POWER9_BASE. It also adds POWER_v2.0
> > with POWER9 DD2 PVR to avoid to trigger kernel POWER9 DD1 workaround
> > in TCG mode.
> >
> > Signed-off-by: Laurent Vivier <lvivier@redhat.com>
> > ---
> > hw/ppc/spapr_cpu_core.c | 5 ++++-
> > target/ppc/cpu-models.c | 6 ++++--
> > target/ppc/cpu-models.h | 1 +
> > 3 files changed, 9 insertions(+), 3 deletions(-)
> >
> > diff --git a/hw/ppc/spapr_cpu_core.c b/hw/ppc/spapr_cpu_core.c
> > index 9fb896b..00918a5 100644
> > --- a/hw/ppc/spapr_cpu_core.c
> > +++ b/hw/ppc/spapr_cpu_core.c
> > @@ -249,8 +249,11 @@ static const char *spapr_core_models[] = {
> > /* POWER8NVL */
> > "POWER8NVL_v1.0",
> >
> > - /* POWER9 */
> > + /* POWER9 DD1 */
> > "POWER9_v1.0",
> > +
> > + /* POWER9 DD2 */
> > + "POWER9_v2.0",
>
> In case you re-spin, what about a more compact listing:
>
> /* POWER9 */
> "POWER9_v1.0",
> "POWER9_v2.0",
>
> ?
>
I second that but anyway:
Reviewed-by: Greg Kurz <groug@kaod.org>
> Anyway, patch looks good to me, so:
>
> Reviewed-by: Thomas Huth <thuth@redhat.com>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2017-07-04 8:52 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-03 13:14 [Qemu-devel] [RFC v3 0/2] target/ppc/cpu-models: set POWER9_v1.0 as POWER9 DD1 Laurent Vivier
2017-07-03 13:14 ` [Qemu-devel] [RFC v3 1/2] " Laurent Vivier
2017-07-04 7:42 ` [Qemu-devel] [Qemu-ppc] " Thomas Huth
2017-07-04 8:51 ` Greg Kurz [this message]
2017-07-04 8:56 ` Laurent Vivier
2017-07-04 9:25 ` David Gibson
2017-07-03 13:14 ` [Qemu-devel] [RFC v3 2/2] target/ppc: move POWER9 DD1 workaround to ppc_cpu_initfn Laurent Vivier
2017-07-04 8:17 ` Thomas Huth
2017-07-04 9:27 ` David Gibson
2017-07-04 11:13 ` [Qemu-devel] [Qemu-ppc] " Thomas Huth
2017-07-04 9:22 ` [Qemu-devel] [RFC v3 0/2] target/ppc/cpu-models: set POWER9_v1.0 as POWER9 DD1 David Gibson
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=20170704105146.6ef17b9f@bahia.lan \
--to=groug@kaod.org \
--cc=clg@kaod.org \
--cc=david@gibson.dropbear.id.au \
--cc=joserz@linux.vnet.ibm.com \
--cc=lvivier@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=qemu-ppc@nongnu.org \
--cc=sbobroff@redhat.com \
--cc=sursingh@redhat.com \
--cc=thuth@redhat.com \
/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).