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 cpu# directory is created per logical CPU in the system,
93 core_siblings_list: human-readable list of the logical CPU
103 thread_siblings_list: human-readable list of cpu#'s hardware
106 See Documentation/admin-guide/cputopology.rst for more information.
114 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
140 See Documentation/admin-guide/pm/cpuidle.rst and
141 Documentation/driver-api/pm/cpuidle.rst for more information.
153 Contact: Linux power management list <linux-pm@vger.kernel.org>
162 latency: (RO) The latency to exit out of this idle state (in
165 power: (RO) The power consumed while in this idle state (in
168 time: (RO) The total time spent in this idle state (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.
203 Contact: Linux power management list <linux-pm@vger.kernel.org>
206 time (in microseconds) this cpu should spend in this idle state
212 Contact: Linux power management list <linux-pm@vger.kernel.org>
214 Idle state usage statistics related to suspend-to-idle.
217 used in suspend-to-idle with suspended timekeeping.
222 Contact: Linux power management list <linux-pm@vger.kernel.org>
224 Total time spent by the CPU in suspend-to-idle (with scheduler
225 tick suspended) after requesting this state.
230 Contact: Linux power management list <linux-pm@vger.kernel.org>
233 while entering suspend-to-idle.
236 Date: pre-git history
237 Contact: linux-pm@vger.kernel.org
245 There are many knobs to tweak in this directory.
247 See files in Documentation/cpu-freq/ for more information.
252 Contact: linux-pm@vger.kernel.org
253 Description: Discover CPUs in the same CPU frequency coordination domain
260 power/performance results for platforms using acpi-cpufreq.
262 This file is only present if the acpi-cpufreq driver is in use.
268 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
271 These files exist in every CPU's cache/index3 directory. Each
287 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
293 More details can be found in
294 Documentation/admin-guide/pm/cpufreq.rst
313 Contact: linux-pm@vger.kernel.org
314 Description: Parameters for the Intel P-state driver
316 Logic for selecting the current P-state in Intel
318 limits for the P-state that will be requested by the
330 More details can be found in
331 Documentation/admin-guide/pm/intel_pstate.rst
336 Linux kernel mailing list <linux-kernel@vger.kernel.org>
340 - WriteAllocate: allocate a memory location to a cache line
342 - ReadAllocate: allocate a memory location to a cache line
344 - ReadWriteAllocate: both writeallocate and readallocate
348 coherency_line_size: the minimum amount of data in bytes that gets
351 level: the cache hierarchy in the multi-level cache configuration
353 number_of_sets: total number of sets in the cache, a set is a
363 size: the total cache size in kB
366 - Instruction: cache that only holds instructions
367 - Data: cache that only caches data
368 - Unified: cache that holds both data and instructions
370 ways_of_associativity: degree of freedom in placing a particular block
371 of memory in the cache
374 - WriteThrough: data is written to both the cache line
375 and to the block in the lower-level memory
376 - WriteBack: data is written only to the cache line and
383 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
388 3 unified cache on each socket in a server and we may
391 Note that id value can be non-contiguous. E.g. level 1
406 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
407 Linux for PowerPC mailing list <linuxppc-dev@ozlabs.org>
414 throttle attributes exported in the 'throttle_stats' directory:
416 - turbo_stat : This file gives the total number of times the max
417 frequency is throttled to lower frequency in turbo (at and above
420 - sub_turbo_stat : This file gives the total number of times the
421 max frequency is throttled to lower frequency in sub-turbo(below
424 - unthrottle : This file gives the total number of times the max
427 - powercap : This file gives the total number of times the max
430 - overtemp : This file gives the total number of times the max
433 - supply_fault : This file gives the total number of times the
436 - overcurrent : This file gives the total number of times the
439 - occ_reset : This file gives the total number of times the max
456 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
457 Linux for PowerPC mailing list <linuxppc-dev@ozlabs.org>
470 Contact: Linux ARM Kernel Mailing list <linux-arm-kernel@lists.infradead.org>
477 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
492 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
497 state of the CPUs in the system. Possible output values:
500 "Vulnerable" CPU is affected and no mitigation in effect
501 "Mitigation: $M" CPU is affected and mitigation $M is in effect
503 See also: Documentation/admin-guide/hw-vuln/index.rst
509 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
529 Contact: linux-pm@vger.kernel.org
532 EPB for the given CPU in a sliding scale 0 - 15, where a value
536 In order to change the EPB value for the CPU, write either
537 a number in the 0 - 15 sliding scale above, or one of the
538 strings: "performance", "balance-performance", "normal",
539 "balance-power", "power" (that represent values reflected by
549 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
563 in TSC-quanta that the CPU can reside in either C0.1
564 or C0.2 state. The time is an unsigned 32-bit number.
565 Note that a value of zero means there is no limit.
570 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
571 Linux for PowerPC mailing list <linuxppc-dev@ozlabs.org>
575 Facility in POWER9 and newer processors. i.e., it is a Secure