diff options
| author | Asaf Nuri Bertizlioğlu <ycistak@gmail.com> | 2026-10-15 20:17:59 +0300 |
|---|---|---|
| committer | Guenter Roeck <linux@roeck-us.net> | 2026-10-19 05:45:07 -0700 |
| commit | 8e9bd28236e633238a7773c9dd809bd87a4db1c2 (patch) | |
| tree | 5a098853b283ddd8be5622a8fbc833561c402e91 /tools/perf/scripts/python/bin | |
| parent | 58d7d43e48044642d22c4c7afc4c5b99103dd684 (diff) | |
| download | linux-8e9bd28236e633238a7773c9dd809bd87a4db1c2.tar.gz linux-8e9bd28236e633238a7773c9dd809bd87a4db1c2.zip | |
hwmon: (coretemp) Document sysfs numbering and label meaning
The documentation says that all sysfs entries are named with their
core_id, and that the "Core X" label contains the processor number.
Neither is accurate. create_core_attrs() numbers the per-core
attributes core_id + 2 and always uses temp1 for the package sensor,
and show_label() prints topology_core_id(), not the logical CPU
number.
The difference is easy to see on hybrid CPUs. On an i7-14700F, the
"Core 4" label is on temp6 and belongs to CPUs 2 and 3, and the
E-cores report core IDs 32 to 43.
Describe the actual numbering.
The mismatch was found by an LLM comparing the documentation with the
code, and verified on the i7-14700F above.
Assisted-by: LLM
Signed-off-by: Asaf Nuri Bertizlioğlu <ycistak@gmail.com>
Tested-by: Ximing Zhang <xzhangjr@gmail.com>
Reviewed-by: Ximing Zhang <xzhangjr@gmail.com>
Link: https://patch.msgid.link/20261015171759.704526-1-ycistak@gmail.com
Signed-off-by: Guenter Roeck <linux@roeck-us.net>
Diffstat (limited to 'tools/perf/scripts/python/bin')
0 files changed, 0 insertions, 0 deletions
