Lines Matching +full:in +full:- +full:kernel
2 Date: pre-git history
3 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
7 Individual CPU attributes are contained in subdirectories
8 named by the kernel's logical CPU number, e.g.:
18 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
19 Description: CPU topology files that describe kernel limits related to
22 kernel_max: the maximum cpu index allowed by the kernel
27 kernel configuration (kernel_max above).
34 present: cpus that have been identified as being present in
37 See Documentation/admin-guide/cputopology.rst for more information.
43 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
58 Contact: Linux memory management mailing list <linux-mm@kvack.org>
65 in NUMA node 2:
67 /sys/devices/system/cpu/cpu42/node2 -> ../../node/node2
77 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
79 to other cores and threads in the same physical package.
81 One cpuX directory is created per logical CPU in the system,
86 core_siblings: internal kernel map of cpuX's hardware threads
89 core_siblings_list: human-readable list of the logical CPU
96 thread_siblings: internal kernel map of cpuX's hardware
99 thread_siblings_list: human-readable list of cpuX's hardware
102 ppin: human-readable Protected Processor Identification
107 See Documentation/admin-guide/cputopology.rst for more information.
116 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
139 See Documentation/admin-guide/pm/cpuidle.rst,
140 Documentation/admin-guide/pm/intel_idle.rst, and
141 Documentation/driver-api/pm/cpuidle.rst for more information.
153 Contact: Linux power management list <linux-pm@vger.kernel.org>
163 latency: (RO) The latency to exit out of this idle state (in
166 power: (RO) The power consumed while in this idle state (in
169 time: (RO) The total time spent in this idle state
170 (in microseconds).
186 Contact: Linux power management list <linux-pm@vger.kernel.org>
194 Contact: Linux power management list <linux-pm@vger.kernel.org>
198 of a particular governor. In the ladder governor, for example,
207 Contact: Linux power management list <linux-pm@vger.kernel.org>
214 Contact: Linux power management list <linux-pm@vger.kernel.org>
217 time (in microseconds) this cpu should spend in this idle state
223 Contact: Linux power management list <linux-pm@vger.kernel.org>
225 Idle state usage statistics related to suspend-to-idle.
228 used in suspend-to-idle with suspended timekeeping.
233 Contact: Linux power management list <linux-pm@vger.kernel.org>
235 Total time spent by the CPU in suspend-to-idle (with scheduler
241 Contact: Linux power management list <linux-pm@vger.kernel.org>
244 while entering suspend-to-idle.
247 Date: pre-git history
248 Contact: linux-pm@vger.kernel.org
256 There are many knobs to tweak in this directory.
258 See files in Documentation/cpu-freq/ for more information.
263 Contact: linux-pm@vger.kernel.org
264 Description: Discover CPUs in the same CPU frequency coordination domain
271 power/performance results for platforms using acpi-cpufreq.
273 This file is only present if the acpi-cpufreq or the cppc-cpufreq
274 drivers are in use.
278 Contact: linux-pm@vger.kernel.org
289 This file is only present if the cppc-cpufreq driver is in use.
293 Contact: linux-pm@vger.kernel.org
299 Read/write an integer represents autonomous activity window (in
312 This file is only present if the cppc-cpufreq driver is in use.
316 Contact: linux-pm@vger.kernel.org
319 Read/write an 8-bit integer from/to this file. This file
328 This file is only present if the cppc-cpufreq driver is in use.
334 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
337 These files exist in every CPU's cache/index3 directory. Each
348 https://www.amd.com/en/support/tech-docs?keyword=bios+kernel
353 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
360 More details can be found in
361 Documentation/admin-guide/pm/cpufreq.rst
380 Contact: linux-pm@vger.kernel.org
381 Description: Parameters for the Intel P-state driver
383 Logic for selecting the current P-state in Intel
385 limits for the P-state that will be requested by the
397 More details can be found in
398 Documentation/admin-guide/pm/intel_pstate.rst
403 Linux kernel mailing list <linux-kernel@vger.kernel.org>
407 - WriteAllocate:
410 - ReadAllocate:
413 - ReadWriteAllocate:
417 the minimum amount of data in bytes that gets
421 the cache hierarchy in the multi-level cache configuration
424 total number of sets in the cache, a set is a
438 the total cache size in kB
441 - Instruction: cache that only holds instructions
442 - Data: cache that only caches data
443 - Unified: cache that holds both data and instructions
446 degree of freedom in placing a particular block
447 of memory in the cache
450 - WriteThrough:
452 and to the block in the lower-level memory
453 - WriteBack:
461 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
466 3 unified cache on each socket in a server and we may
469 Note that id value can be non-contiguous. E.g. level 1
484 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
485 Linux for PowerPC mailing list <linuxppc-dev@lists.ozlabs.org>
492 throttle attributes exported in the 'throttle_stats' directory:
494 - turbo_stat : This file gives the total number of times the max
495 frequency is throttled to lower frequency in turbo (at and above
498 - sub_turbo_stat : This file gives the total number of times the
499 max frequency is throttled to lower frequency in sub-turbo(below
502 - unthrottle : This file gives the total number of times the max
505 - powercap : This file gives the total number of times the max
508 - overtemp : This file gives the total number of times the max
511 - supply_fault : This file gives the total number of times the
514 - overcurrent : This file gives the total number of times the
517 - occ_reset : This file gives the total number of times the max
534 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
535 Linux for PowerPC mailing list <linuxppc-dev@lists.ozlabs.org>
550 Contact: Linux ARM Kernel Mailing list <linux-arm-kernel@lists.infradead.org>
558 Contact: Linux ARM Kernel Mailing list <linux-arm-kernel@lists.infradead.org>
559 Description: Identifies the subset of CPUs in the system that can execute
560 AArch32 (32-bit ARM) applications. If present, the same format as
567 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
591 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
596 state of the CPUs in the system. Possible output values:
600 "Vulnerable" CPU is affected and no mitigation in effect
601 "Mitigation: $M" CPU is affected and mitigation $M is in effect
604 See also: Documentation/admin-guide/hw-vuln/index.rst
610 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
634 Contact: linux-pm@vger.kernel.org
637 EPB for the given CPU in a sliding scale 0 - 15, where a value
641 In order to change the EPB value for the CPU, write either
642 a number in the 0 - 15 sliding scale above, or one of the
643 strings: "performance", "balance-performance", "normal",
644 "balance-power", "power" (that represent values reflected by
654 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
668 in TSC-quanta that the CPU can reside in either C0.1
669 or C0.2 state. The time is an unsigned 32-bit number.
676 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
679 This directory is only present when running as an SEV-SNP guest.
682 the SEV-SNP guest is running.
687 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
688 Linux for PowerPC mailing list <linuxppc-dev@lists.ozlabs.org>
692 Facility in POWER9 and newer processors. i.e., it is a Secure
697 Contact: Linux for PowerPC mailing list <linuxppc-dev@lists.ozlabs.org>
701 a 64-bit counter which provides an estimate of the
708 Contact: Linux for PowerPC mailing list <linuxppc-dev@lists.ozlabs.org>
712 (SPURR) is a 64-bit counter that provides a frequency
720 Contact: Linux for PowerPC mailing list <linuxppc-dev@lists.ozlabs.org>
728 Contact: Linux for PowerPC mailing list <linuxppc-dev@lists.ozlabs.org>
736 Contact: Linux ARM Kernel Mailing list <linux-arm-kernel@lists.infradead.org>
750 See also: Documentation/arch/arm64/memory-tagging-extension.rst
754 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
756 (RO) the list of CPUs that are in nohz_full mode.
761 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
764 participate in load balancing. These CPUs are set by
769 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
771 (RO) indicates whether or not the kernel updates relevant kexec
773 need to reload kdump kernel.
777 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>