diff options
author | Andreas Färber <afaerber@suse.de> | 2013-08-05 22:59:46 +0200 |
---|---|---|
committer | Anthony Liguori <aliguori@us.ibm.com> | 2013-08-07 12:47:00 -0500 |
commit | a7d6b9f084765a834110bb9a2a0329b1a96de792 (patch) | |
tree | 66e9b85191a5a91f5acf40780582695d29dd7bdc /target-ppc/cpu-models.h | |
parent | 0dd5ce38fbeb2fb97b01cc8c1c97292211e48ee6 (diff) |
target-ppc: Fix POWER7+ model
Commit 03a15a5436ed7723f406f15cc3798aa9991e75b5 claimed to add a POWER7+
model but instead added a "POWER7P" model, with an unhelpful "POWER7P"
description on top. Fix this to "POWER7+" as we already have "POWER3+",
"POWER4+" and "POWER5+" and there being no reason to deviate with the
user-visible command line -cpu POWER7P from the marketing name POWER7+.
Further, don't needlessly deviate from the scheme of naming PVR constant,
QOM type and device description after the exact revision that is in fact
encoded in the PVR used.
That way, we can change the user-friendly alias -cpu POWER7+ to point to a
different revision if we so desire, while not polluting the type namespace.
This naming scheme is sensible and completely orthogonal to how PVRs may
or may not get matched to CPU types.
Cc: Alexey Kardashevskiy <aik@ozlabs.ru>
Signed-off-by: Andreas Färber <afaerber@suse.de>
Signed-off-by: Andreas Färber <afaerber@suse.de>
Message-id: 1375736387-8429-1-git-send-email-afaerber@suse.de
Signed-off-by: Anthony Liguori <aliguori@us.ibm.com>
Diffstat (limited to 'target-ppc/cpu-models.h')
-rw-r--r-- | target-ppc/cpu-models.h | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/target-ppc/cpu-models.h b/target-ppc/cpu-models.h index c3c78d121c..58c4ea0bbe 100644 --- a/target-ppc/cpu-models.h +++ b/target-ppc/cpu-models.h @@ -556,7 +556,7 @@ enum { CPU_POWERPC_POWER7_v20 = 0x003F0200, CPU_POWERPC_POWER7_v21 = 0x003F0201, CPU_POWERPC_POWER7_v23 = 0x003F0203, - CPU_POWERPC_POWER7P = 0x004A0201, + CPU_POWERPC_POWER7P_v21 = 0x004A0201, CPU_POWERPC_POWER8_v10 = 0x004B0100, CPU_POWERPC_970 = 0x00390202, CPU_POWERPC_970FX_v10 = 0x00391100, |