michaelh/zephyr
1
0
Fork 0
Code Releases Activity

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

Browse source 
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 <daniel.leung@intel.com>
This commit is contained in:
Daniel Leung 2024-10-01 11:12:28 -07:00 • committed by Anas Nashif
commit a6c1f80f46
3 changed files with 18 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

6
tests/benchmarks/latency_measure/boards/intel_adsp_ace15_mtpm_sim.conf Normal file
View file

@ -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

6
tests/benchmarks/latency_measure/boards/intel_adsp_ace20_lnl_sim.conf Normal file
View file

@ -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

6
tests/benchmarks/latency_measure/boards/intel_adsp_ace30_ptl_sim.conf Normal file
View file

@ -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