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>
This commit is contained in:
parent
2428673638
commit
f5f16ae4fa
@ -268,7 +268,7 @@ int get_core_sibling(int cpu_no)
|
||||
while (token) {
|
||||
sibling_cpu_no = atoi(token);
|
||||
/* Skipping core 0 as we don't want to run test on core 0 */
|
||||
if (sibling_cpu_no != 0)
|
||||
if (sibling_cpu_no != 0 && sibling_cpu_no != cpu_no)
|
||||
break;
|
||||
token = strtok(NULL, "-,");
|
||||
}
|
||||
|
Loading…
x
Reference in New Issue
Block a user