diff options
author | Ilpo Järvinen <ilpo.jarvinen@linux.intel.com> | 2023-12-15 17:05:15 +0200 |
---|---|---|
committer | Shuah Khan <skhan@linuxfoundation.org> | 2024-02-13 13:56:45 -0700 |
commit | 345e8abe4c355bc24bab3f4a5634122e55be8665 (patch) | |
tree | ee0fc4cc4080d9b98408f0e4a74ae91a46e3809f /tools/perf/scripts/python/exported-sql-viewer.py | |
parent | 6874f6ed92df1e95ff815692b6bf6aa98e4c925b (diff) | |
download | linux-345e8abe4c355bc24bab3f4a5634122e55be8665.tar.gz linux-345e8abe4c355bc24bab3f4a5634122e55be8665.tar.bz2 linux-345e8abe4c355bc24bab3f4a5634122e55be8665.zip |
selftests/resctrl: Get domain id from cache id
Domain id is acquired differently depending on CPU. AMD tests use id
from L3 cache, whereas CPUs from other vendors base the id on topology
package id. In order to support L2 CAT test, this has to be
generalized.
The driver side code seems to get the domain ids from cache ids so the
approach used by the AMD branch seems to match the kernel-side code. It
will also work with L2 domain IDs as long as the cache level is
generalized.
Using the topology id was always fragile due to mismatch with the
kernel-side way to acquire the domain id. It got incorrect domain id,
e.g., when Cluster-on-Die (CoD) is enabled for CPU (but CoD is not well
suited for resctrl in the first place so it has not been a big issue if
tests don't work correctly with it).
Taking all the above into account, generalize acquiring the domain id
by taking it from the cache id and do not hard-code the cache level.
Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Reviewed-by: Reinette Chatre <reinette.chatre@intel.com>
Signed-off-by: Shuah Khan <skhan@linuxfoundation.org>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions