Lines Matching +full:no +full:- +full:tick +full:- +full:in +full:- +full:suspend
2 Date: pre-git history
3 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
7 Individual CPU attributes are contained in subdirectories
18 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
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,
89 core_siblings_list: human-readable list of the logical CPU
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.
115 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
135 See Documentation/admin-guide/pm/cpuidle.rst and
136 Documentation/driver-api/pm/cpuidle.rst for more information.
148 Contact: Linux power management list <linux-pm@vger.kernel.org>
158 latency: (RO) The latency to exit out of this idle state (in
161 power: (RO) The power consumed while in this idle state (in
164 time: (RO) The total time spent in this idle state
165 (in microseconds).
181 Contact: Linux power management list <linux-pm@vger.kernel.org>
189 Contact: Linux power management list <linux-pm@vger.kernel.org>
193 of a particular governor. In the ladder governor, for example,
197 lighter state still is disabled, then this has no effect.
202 Contact: Linux power management list <linux-pm@vger.kernel.org>
209 Contact: Linux power management list <linux-pm@vger.kernel.org>
212 time (in microseconds) this cpu should spend in this idle state
218 Contact: Linux power management list <linux-pm@vger.kernel.org>
220 Idle state usage statistics related to suspend-to-idle.
223 used in suspend-to-idle with suspended timekeeping.
228 Contact: Linux power management list <linux-pm@vger.kernel.org>
230 Total time spent by the CPU in suspend-to-idle (with scheduler
231 tick suspended) after requesting this state.
236 Contact: Linux power management list <linux-pm@vger.kernel.org>
239 while entering suspend-to-idle.
242 Date: pre-git history
243 Contact: linux-pm@vger.kernel.org
251 There are many knobs to tweak in this directory.
253 See files in Documentation/cpu-freq/ for more information.
258 Contact: linux-pm@vger.kernel.org
259 Description: Discover CPUs in the same CPU frequency coordination domain
266 power/performance results for platforms using acpi-cpufreq.
268 This file is only present if the acpi-cpufreq or the cppc-cpufreq
269 drivers are in use.
275 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
278 These files exist in every CPU's cache/index3 directory. Each
289 https://www.amd.com/en/support/tech-docs?keyword=bios+kernel
294 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
301 More details can be found in
302 Documentation/admin-guide/pm/cpufreq.rst
321 Contact: linux-pm@vger.kernel.org
322 Description: Parameters for the Intel P-state driver
324 Logic for selecting the current P-state in Intel
326 limits for the P-state that will be requested by the
338 More details can be found in
339 Documentation/admin-guide/pm/intel_pstate.rst
344 Linux kernel mailing list <linux-kernel@vger.kernel.org>
348 - WriteAllocate:
351 - ReadAllocate:
354 - ReadWriteAllocate:
361 the minimum amount of data in bytes that gets
365 the cache hierarchy in the multi-level cache configuration
368 total number of sets in the cache, a set is a
382 the total cache size in kB
385 - Instruction: cache that only holds instructions
386 - Data: cache that only caches data
387 - Unified: cache that holds both data and instructions
390 degree of freedom in placing a particular block
391 of memory in the cache
394 - WriteThrough:
396 and to the block in the lower-level memory
397 - WriteBack:
405 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
410 3 unified cache on each socket in a server and we may
413 Note that id value can be non-contiguous. E.g. level 1
428 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
429 Linux for PowerPC mailing list <linuxppc-dev@ozlabs.org>
436 throttle attributes exported in the 'throttle_stats' directory:
438 - turbo_stat : This file gives the total number of times the max
439 frequency is throttled to lower frequency in turbo (at and above
442 - sub_turbo_stat : This file gives the total number of times the
443 max frequency is throttled to lower frequency in sub-turbo(below
446 - unthrottle : This file gives the total number of times the max
449 - powercap : This file gives the total number of times the max
452 - overtemp : This file gives the total number of times the max
455 - supply_fault : This file gives the total number of times the
458 - overcurrent : This file gives the total number of times the
461 - occ_reset : This file gives the total number of times the max
478 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
479 Linux for PowerPC mailing list <linuxppc-dev@ozlabs.org>
493 Contact: Linux ARM Kernel Mailing list <linux-arm-kernel@lists.infradead.org>
501 Contact: Linux ARM Kernel Mailing list <linux-arm-kernel@lists.infradead.org>
502 Description: Identifies the subset of CPUs in the system that can execute
503 AArch32 (32-bit ARM) applications. If present, the same format as
510 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
528 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
533 state of the CPUs in the system. Possible output values:
537 "Vulnerable" CPU is affected and no mitigation in effect
538 "Mitigation: $M" CPU is affected and mitigation $M is in effect
541 See also: Documentation/admin-guide/hw-vuln/index.rst
547 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
569 Contact: linux-pm@vger.kernel.org
572 EPB for the given CPU in a sliding scale 0 - 15, where a value
576 In order to change the EPB value for the CPU, write either
577 a number in the 0 - 15 sliding scale above, or one of the
578 strings: "performance", "balance-performance", "normal",
579 "balance-power", "power" (that represent values reflected by
589 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
603 in TSC-quanta that the CPU can reside in either C0.1
604 or C0.2 state. The time is an unsigned 32-bit number.
605 Note that a value of zero means there is no limit.
610 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
611 Linux for PowerPC mailing list <linuxppc-dev@ozlabs.org>
615 Facility in POWER9 and newer processors. i.e., it is a Secure
620 Contact: Linux for PowerPC mailing list <linuxppc-dev@ozlabs.org>
624 a 64-bit counter which provides an estimate of the
631 Contact: Linux for PowerPC mailing list <linuxppc-dev@ozlabs.org>
635 (SPURR) is a 64-bit counter that provides a frequency
643 Contact: Linux for PowerPC mailing list <linuxppc-dev@ozlabs.org>
651 Contact: Linux for PowerPC mailing list <linuxppc-dev@ozlabs.org>
659 Contact: Linux ARM Kernel Mailing list <linux-arm-kernel@lists.infradead.org>
673 See also: Documentation/arm64/memory-tagging-extension.rst
677 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
679 (RO) the list of CPUs that are in nohz_full mode.
684 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
687 participate in load balancing. These CPUs are set by