tests: benchmarks/sched: limit CPU to 1 for Intel ADSP ACE

ycsin · nashif · commit e0ce096b9127 · 2024-11-16T14:07:08.000-05:00
Due to addition of busy threads running on other cores, and
the simulator runs in single thread bouncing through all cores,
we are wasting quite a bit of time just busy waiting. This makes
each simulator run too long for CI. So limit CPU number to 1.

Signed-off-by: Daniel Leung &lt;daniel.leung@intel.com&gt;
Signed-off-by: Yong Cong Sin &lt;ycsin@meta.com&gt;
diff --git a/tests/benchmarks/sched/boards/intel_adsp_ace15_mtpm_sim.conf b/tests/benchmarks/sched/boards/intel_adsp_ace15_mtpm_sim.conf
@@ -0,0 +1,6 @@
+# Due to addition of busy threads running on other cores,
+# and the simulator runs in single thread bouncing through
+# all cores, we are wasting quite a bit of time just busy
+# waiting. This makes each simulator run too long for CI.
+# So limit CPU number to 1.
+CONFIG_MP_MAX_NUM_CPUS=1
diff --git a/tests/benchmarks/sched/boards/intel_adsp_ace20_lnl_sim.conf b/tests/benchmarks/sched/boards/intel_adsp_ace20_lnl_sim.conf
@@ -0,0 +1,6 @@
+# Due to addition of busy threads running on other cores,
+# and the simulator runs in single thread bouncing through
+# all cores, we are wasting quite a bit of time just busy
+# waiting. This makes each simulator run too long for CI.
+# So limit CPU number to 1.
+CONFIG_MP_MAX_NUM_CPUS=1
diff --git a/tests/benchmarks/sched/boards/intel_adsp_ace30_ptl_sim.conf b/tests/benchmarks/sched/boards/intel_adsp_ace30_ptl_sim.conf
@@ -0,0 +1,6 @@
+# Due to addition of busy threads running on other cores,
+# and the simulator runs in single thread bouncing through
+# all cores, we are wasting quite a bit of time just busy
+# waiting. This makes each simulator run too long for CI.
+# So limit CPU number to 1.
+CONFIG_MP_MAX_NUM_CPUS=1
