fvp: move a710 to 8 core test
With 11.26.11 FVP models a710 is a 8 core FVP, so move tests
to use 8 cores rather than 4 cores.
If we setup as 4 cores from FVP kernel still recognises as 8 core system.
[...]
rcu: RCU restricting CPUs from NR_CPUS=256 to nr_cpu_ids=8.
[...]
This means kernel can schedule init.sh on any of the core ids.
But since we fail to bring up core4 to 7 and we schedule on any of
these cores will eventually lead to a hang with init.sh
not mounting the rootfs, if init.sh is run on core4 to 7.
Also in ci scripts we wait for shell prompt "#" for test to pass
which may not happen when init.sh fails.
Change-Id: Iadd87cbbe8bbb2d456496b9ce65e785f686b66af
Signed-off-by: Govindraj Raja <govindraj.raja@arm.com>
diff --git a/fvp_utils.sh b/fvp_utils.sh
index e273319..b6f850a 100644
--- a/fvp_utils.sh
+++ b/fvp_utils.sh
@@ -90,7 +90,7 @@
[cortex-a78aex4]="${fvp_arm_std_library};FVP_Base_Cortex-A78AE"
[cortex-a78cx4]="${fvp_arm_std_library};FVP_Base_Cortex-A78C"
[cortex-x2]="${fvp_arm_std_library};FVP_Base_Cortex-X2"
-[cortex-a710]="${fvp_arm_std_library};FVP_Base_Cortex-A710"
+[cortex-a710x8]="${fvp_arm_std_library};FVP_Base_Cortex-A710"
[neoverse_e1]="${fvp_arm_std_library_11_24};FVP_Base_Neoverse-E1"
[neoverse_n1]="${fvp_arm_std_library};FVP_Base_Neoverse-N1"
[neoverse_n2]="${fvp_arm_std_library};FVP_Base_Neoverse-N2"