Spdk/test/scheduler
Michal Berger 5ad2877dc4 test/scheduler: Use CPU list rather than cpumask
When we select CPUs for the scheduler tests we pick up all siblings
from given core. On some nodes in the CI these threads may have IDs
in ranges that simply overflow during the shift operation ( > 62).

To avoid this, use a list instead of a mask. Also, deny all threads
with IDs > 127 as DPDK doesn't support them anyway.

Signed-off-by: Michal Berger <michal.berger@intel.com>
Change-Id: Ib83649a762cb31a460184d1e0b594c112aea2bab
Reviewed-on: https://review.spdk.io/gerrit/c/spdk/spdk/+/16604
Reviewed-by: Tomasz Zawadzki <tomasz.zawadzki@intel.com>
Reviewed-by: Konrad Sztyber <konrad.sztyber@intel.com>
Tested-by: SPDK CI Jenkins <sys_sgci@intel.com>
2023-03-01 08:55:26 +00:00
..
cgroups.sh Add SPDX header to various files 2022-11-29 08:27:51 +00:00
common.sh test/scheduler: Use CPU list rather than cpumask 2023-03-01 08:55:26 +00:00
governor.sh add (c) and SPDX header to bash files as needed 2022-11-29 08:27:51 +00:00
idle.sh test/scheduler: Use CPU list rather than cpumask 2023-03-01 08:55:26 +00:00
interrupt.sh add (c) and SPDX header to bash files as needed 2022-11-29 08:27:51 +00:00
isolate_cores.sh Add SPDX header to various files 2022-11-29 08:27:51 +00:00
load_balancing.sh add (c) and SPDX header to bash files as needed 2022-11-29 08:27:51 +00:00
rdmsr.pl Add SPDX header to various files 2022-11-29 08:27:51 +00:00
scheduler.sh add (c) and SPDX header to bash files as needed 2022-11-29 08:27:51 +00:00