summaryrefslogtreecommitdiff
path: root/kernel/pid_sysctl.h
diff options
context:
space:
mode:
authorKan Liang <kan.liang@linux.intel.com>2023-11-16 17:22:44 +0300
committerPeter Zijlstra <peterz@infradead.org>2023-11-17 12:54:53 +0300
commit3877d55a0db2688c2e4ab8a319614a0c81f8e2d2 (patch)
tree60014529a248faf664a09dbcb998b27f9ca73a31 /kernel/pid_sysctl.h
parentc3dd1995620cdcd65cf4944c4164b0dbc16e557c (diff)
downloadlinux-3877d55a0db2688c2e4ab8a319614a0c81f8e2d2.tar.xz
perf/x86/intel/cstate: Add Sierra Forest support
A new module C6 Residency Counter is introduced in the Sierra Forest. The scope of the new counter is module (A cluster of cores shared L2 cache). Create a brand new cstate_module PMU to profile the new counter. The only differences between the new cstate_module PMU and the existing cstate PMU are the scope and events. Regarding the choice of the new cstate_module PMU name, the current naming rule of a cstate PMU is "cstate_" + the scope of the PMU. The scope of the PMU is the cores shared L2. On SRF, Intel calls it "module", while the internal Linux sched code calls it "cluster". The "cstate_module" is used as the new PMU name, because - The Cstate PMU driver is a Intel specific driver. It doesn't impact other ARCHs. The name makes it consistent with the documentation. - The "cluster" mainly be used by the scheduler developer, while the user of cstate PMU is more likely a researcher reading HW docs and optimizing power. - In the Intel's SDM, the "cluster" has a different meaning/scope for topology. Using it will mislead the end users. Besides the module C6, the core C1/C6 and pkg C6 residency counters are supported in the Sierra Forest as well. Suggested-by: Artem Bityutskiy <artem.bityutskiy@linux.intel.com> Signed-off-by: Kan Liang <kan.liang@linux.intel.com> Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Link: https://lore.kernel.org/r/20231116142245.1233485-3-kan.liang@linux.intel.com
Diffstat (limited to 'kernel/pid_sysctl.h')
0 files changed, 0 insertions, 0 deletions