qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Laurent Vivier <lvivier@redhat.com>
To: David Gibson <david@gibson.dropbear.id.au>
Cc: Thomas Huth <thuth@redhat.com>,
	qemu-ppc@nongnu.org, qemu-devel@nongnu.org,
	Laurent Vivier <lvivier@redhat.com>
Subject: [Qemu-devel] [PATCH] target/ppc/cpu-models: set POWER9_v1.0 as POWER9 DD1
Date: Thu, 22 Jun 2017 13:26:48 +0200	[thread overview]
Message-ID: <20170622112648.24815-1-lvivier@redhat.com> (raw)

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.

Signed-off-by: Laurent Vivier <lvivier@redhat.com>
---
 target/ppc/cpu-models.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/target/ppc/cpu-models.c b/target/ppc/cpu-models.c
index 4d3e635..a22363c 100644
--- a/target/ppc/cpu-models.c
+++ b/target/ppc/cpu-models.c
@@ -1144,7 +1144,7 @@
     POWERPC_DEF("970_v2.2",      CPU_POWERPC_970_v22,                970,
                 "PowerPC 970 v2.2")
 
-    POWERPC_DEF("POWER9_v1.0",   CPU_POWERPC_POWER9_BASE,            POWER9,
+    POWERPC_DEF("POWER9_v1.0",   CPU_POWERPC_POWER9_DD1,             POWER9,
                 "POWER9 v1.0")
 
     POWERPC_DEF("970fx_v1.0",    CPU_POWERPC_970FX_v10,              970,
-- 
2.9.4

             reply	other threads:[~2017-06-22 11:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-22 11:26 Laurent Vivier [this message]
2017-06-22 11:31 ` [Qemu-devel] [PATCH] target/ppc/cpu-models: set POWER9_v1.0 as POWER9 DD1 Thomas Huth
2017-06-23  9:21   ` David Gibson
2017-06-23 14:10     ` Laurent Vivier
2017-06-28  1:42       ` [Qemu-devel] [Qemu-ppc] " joserz
2017-06-28  7:09         ` Thomas Huth
2017-06-28  8:18           ` David Gibson
2017-06-28  9:11             ` Cédric Le Goater
2017-06-28  9:18               ` Laurent Vivier
2017-06-28 10:23                 ` Cédric Le Goater
2017-06-28 11:59                   ` Greg Kurz
2017-06-28 16:18                     ` Laurent Vivier
2017-06-28 16:41                       ` Greg Kurz
2017-06-29  5:37                         ` Suraj Jitindar Singh
2017-06-29  5:42                           ` Suraj Jitindar Singh
2017-06-30  7:12                             ` David Gibson
2017-06-30  8:52                               ` Laurent Vivier
2017-06-29  6:44                           ` Thomas Huth
2017-06-29 15:05                             ` Eric Blake
2017-06-30  7:14                       ` David Gibson
2017-06-30  7:56                         ` Cédric Le Goater
2017-06-30 10:36                           ` Michael Ellerman
2017-06-28 10:59         ` Laurent Vivier
2017-06-23 16:05     ` [Qemu-devel] " Thomas Huth
2017-06-28  0:58       ` [Qemu-devel] [Qemu-ppc] " Suraj Jitindar Singh

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=20170622112648.24815-1-lvivier@redhat.com \
    --to=lvivier@redhat.com \
    --cc=david@gibson.dropbear.id.au \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@nongnu.org \
    --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).