aboutsummaryrefslogtreecommitdiff
path: root/target-ppc/cpu-models.c
diff options
context:
space:
mode:
authorAlexey Kardashevskiy <aik@ozlabs.ru>2013-11-19 12:39:15 +1100
committerAlexander Graf <agraf@suse.de>2013-12-20 01:57:58 +0100
commitb650d6a2fcb77e2e42872ebd102ba387d547ab77 (patch)
tree8b75491ccb7c459cf8ae89e83c826567c06aed11 /target-ppc/cpu-models.c
parent86e61ce3d0e4806519c79f2555f20b7b3283bdab (diff)
downloadqemu-b650d6a2fcb77e2e42872ebd102ba387d547ab77.zip
qemu-b650d6a2fcb77e2e42872ebd102ba387d547ab77.tar.gz
qemu-b650d6a2fcb77e2e42872ebd102ba387d547ab77.tar.bz2
target-ppc: move POWER7+ to a separate family
So far POWER7+ was a part of POWER7 family. However it has a different PVR base value so in order to support PVR masks, it needs a separate family class. This adds a new family class, PVR base and mask values and moves Power7+ v2.1 CPU to a new family. The class init function is copied from the POWER7 family. This defines a firmware name for the new family as "PowerPC,POWER7+" instead of previously used "PowerPC,POWER7" from the POWER7 family. The reason for that is that the Sapphire firmware (a h0st firmware) uses "PowerPC,POWER7+" already and since no specification defines exactly the CPU nodes naming in the device tree, we better stay in sync with the host firmware. Signed-off-by: Alexey Kardashevskiy <aik@ozlabs.ru> Signed-off-by: Alexander Graf <agraf@suse.de>
Diffstat (limited to 'target-ppc/cpu-models.c')
-rw-r--r--target-ppc/cpu-models.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/target-ppc/cpu-models.c b/target-ppc/cpu-models.c
index 04d88c5..7c9466f 100644
--- a/target-ppc/cpu-models.c
+++ b/target-ppc/cpu-models.c
@@ -1140,7 +1140,7 @@
"POWER7 v2.1")
POWERPC_DEF("POWER7_v2.3", CPU_POWERPC_POWER7_v23, POWER7,
"POWER7 v2.3")
- POWERPC_DEF("POWER7+_v2.1", CPU_POWERPC_POWER7P_v21, POWER7,
+ POWERPC_DEF("POWER7+_v2.1", CPU_POWERPC_POWER7P_v21, POWER7P,
"POWER7+ v2.1")
POWERPC_DEF("POWER8_v1.0", CPU_POWERPC_POWER8_v10, POWER8,
"POWER8 v1.0")