From: Alexey Kardashevskiy <aik@ozlabs.ru>
To: David Gibson <david@gibson.dropbear.id.au>, agraf@suse.de
Cc: lvivier@redhat.com, thuth@redhat.com, qemu-devel@nongnu.org,
abologna@redhat.com, qemu-ppc@nongnu.org,
mdroth@linuc.vnet.ibm.com, afaerber@suse.de
Subject: Re: [Qemu-devel] [PATCH] target-ppc: Add POWER8E_v2.1 CPU model.
Date: Wed, 8 Jul 2015 14:10:28 +1000 [thread overview]
Message-ID: <559CA2B4.3090303@ozlabs.ru> (raw)
In-Reply-To: <1436327021-14744-1-git-send-email-david@gibson.dropbear.id.au>
On 07/08/2015 01:43 PM, David Gibson wrote:
> From: Andrea Bolognani <abologna@redhat.com>
>
> Add a missing PVR value for the POWER8E v2.1 CPU. Information taken
> from the kernel cputable.
>
> Signed-off-by: Andrea Bolognani <abologna@redhat.com>
> Signed-off-by: David Gibson <david@gibson.dropbear.id.au>
> ---
> target-ppc/cpu-models.c | 4 +++-
> target-ppc/cpu-models.h | 1 +
> 2 files changed, 4 insertions(+), 1 deletion(-)
>
> Alex,
>
> Not sure if this counts as a bugfix which can be merged now we're in
> the hard freeze. The lack of it does mean we can't work on one of our
> dev machines which has this CPU.
Why is this a stopper? We stopped bothering with exact PVRs some time ago
and -cpu POWER8 or -cpu host still work.
>
> diff --git a/target-ppc/cpu-models.c b/target-ppc/cpu-models.c
> index 4d5ab4b..9d8769b 100644
> --- a/target-ppc/cpu-models.c
> +++ b/target-ppc/cpu-models.c
> @@ -1140,6 +1140,8 @@
> "POWER7+ v2.1")
> POWERPC_DEF("POWER8E_v1.0", CPU_POWERPC_POWER8E_v10, POWER8,
> "POWER8E v1.0")
> + POWERPC_DEF("POWER8E_v2.1", CPU_POWERPC_POWER8E_v21, POWER8,
> + "POWER8E v2.1")
> POWERPC_DEF("POWER8_v1.0", CPU_POWERPC_POWER8_v10, POWER8,
> "POWER8 v1.0")
> POWERPC_DEF("970_v2.2", CPU_POWERPC_970_v22, 970,
> @@ -1389,7 +1391,7 @@ PowerPCCPUAlias ppc_cpu_aliases[] = {
> { "POWER5gs", "POWER5+_v2.1" },
> { "POWER7", "POWER7_v2.3" },
> { "POWER7+", "POWER7+_v2.1" },
> - { "POWER8E", "POWER8E_v1.0" },
> + { "POWER8E", "POWER8E_v2.1" },
> { "POWER8", "POWER8_v1.0" },
> { "970", "970_v2.2" },
> { "970fx", "970fx_v3.1" },
> diff --git a/target-ppc/cpu-models.h b/target-ppc/cpu-models.h
> index 9d80e72..add31c6 100644
> --- a/target-ppc/cpu-models.h
> +++ b/target-ppc/cpu-models.h
> @@ -558,6 +558,7 @@ enum {
> CPU_POWERPC_POWER7P_v21 = 0x004A0201,
> CPU_POWERPC_POWER8E_BASE = 0x004B0000,
> CPU_POWERPC_POWER8E_v10 = 0x004B0100,
> + CPU_POWERPC_POWER8E_v21 = 0x004B0201,
> CPU_POWERPC_POWER8_BASE = 0x004D0000,
> CPU_POWERPC_POWER8_v10 = 0x004D0100,
> CPU_POWERPC_970_v22 = 0x00390202,
>
--
Alexey
next prev parent reply other threads:[~2015-07-08 4:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-08 3:43 [Qemu-devel] [PATCH] target-ppc: Add POWER8E_v2.1 CPU model David Gibson
2015-07-08 4:10 ` Alexey Kardashevskiy [this message]
2015-07-08 5:37 ` David Gibson
2015-07-08 6:40 ` Alexey Kardashevskiy
2015-07-08 6:45 ` David Gibson
2015-07-08 7:02 ` Alexey Kardashevskiy
2015-07-08 16:35 ` Andrea Bolognani
2015-07-09 2:35 ` Alexey Kardashevskiy
2015-07-09 10:03 ` Andrea Bolognani
2015-07-10 5:19 ` Alexey Kardashevskiy
2015-07-10 9:19 ` Andrea Bolognani
2015-07-13 3:11 ` Alexey Kardashevskiy
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=559CA2B4.3090303@ozlabs.ru \
--to=aik@ozlabs.ru \
--cc=abologna@redhat.com \
--cc=afaerber@suse.de \
--cc=agraf@suse.de \
--cc=david@gibson.dropbear.id.au \
--cc=lvivier@redhat.com \
--cc=mdroth@linuc.vnet.ibm.com \
--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).