selftests/resctrl: Ensure sibling CPU is not same as original CPU
authorReinette Chatre <reinette.chatre@intel.com>
Wed, 17 Mar 2021 02:22:39 +0000 (02:22 +0000)
committerShuah Khan <skhan@linuxfoundation.org>
Fri, 2 Apr 2021 19:51:43 +0000 (13:51 -0600)
commitf5f16ae4fae9d4d51aa365a0e1d84d368bef53ea
tree10b25c87595aa3bde93fb2567328a96351032d90
parent2428673638ea28fa93d2a38b1c3e8d70122b00ee
selftests/resctrl: Ensure sibling CPU is not same as original CPU

The resctrl tests can accept a CPU on which the tests are run and use
default of CPU #1 if it is not provided. In the CAT test a "sibling CPU"
is determined that is from the same package where another thread will be
run.

The current algorithm with which a "sibling CPU" is determined does not
take the provided/default CPU into account and when that CPU is the
first CPU in a package then the "sibling CPU" will be selected to be the
same CPU since it starts by picking the first CPU from core_siblings_list.

Fix the "sibling CPU" selection by taking the provided/default CPU into
account and ensuring a sibling that is a different CPU is selected.

Tested-by: Babu Moger <babu.moger@amd.com>
Signed-off-by: Reinette Chatre <reinette.chatre@intel.com>
Signed-off-by: Fenghua Yu <fenghua.yu@intel.com>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
tools/testing/selftests/resctrl/resctrlfs.c