Home
last modified time | relevance | path

Searched +full:p +full:- +full:states (Results 1 – 25 of 51) sorted by relevance

123

/Documentation/admin-guide/pm/
Dintel_pstate.rst1 .. SPDX-License-Identifier: GPL-2.0
22 Documentation/admin-guide/pm/cpufreq.rst if you have not done that yet.]
24 For the processors supported by ``intel_pstate``, the P-state concept is broader
27 information about that). For this reason, the representation of P-states used
32 ``intel_pstate`` maps its internal representation of P-states to frequencies too
38 Since the hardware P-state selection interface used by ``intel_pstate`` is
43 time the corresponding CPU is taken offline and need to be re-initialized when
47 only way to pass early-configuration-time parameters to it is via the kernel
66 -----------
69 hardware-managed P-states (HWP) support. If it works in this mode, the
[all …]
Dcpufreq.rst1 .. SPDX-License-Identifier: GPL-2.0
20 Operating Performance Points or P-states (in ACPI terminology). As a rule,
24 time (or the more power is drawn) by the CPU in the given P-state. Therefore
29 as possible and then there is no reason to use any P-states different from the
30 highest one (i.e. the highest-performance frequency/voltage configuration
38 put into different P-states.
41 capacity, so as to decide which P-states to put the CPUs into. Of course, since
64 information on the available P-states (or P-state ranges in some cases) and
65 access platform-specific hardware interfaces to change CPU P-states as requested
70 performance scaling algorithms for P-state selection can be represented in a
[all …]
Damd-pstate.rst1 .. SPDX-License-Identifier: GPL-2.0
5 ``amd-pstate`` CPU Performance Scaling Driver
16 ``amd-pstate`` is the AMD CPU performance scaling driver that introduces a
20 than legacy ACPI hardware P-States. Current AMD CPU/APU platforms are using
21 the ACPI P-states driver to manage CPU frequency and clocks with switching
22 only in 3 P-states. CPPC replaces the ACPI P-states controls and allows a
23 flexible, low-latency interface for the Linux kernel to directly
26 ``amd-pstate`` leverages the Linux kernel governors such as ``schedutil``,
30 Volume 2: System Programming [1]_). Currently, ``amd-pstate`` supports basic
40 continuous, abstract, and unit-less performance value in a scale that is
[all …]
Dcpuidle.rst1 .. SPDX-License-Identifier: GPL-2.0
19 Modern processors are generally able to enter states in which the execution of
21 memory or executed. Those states are the *idle* states of the processor.
23 Since part of the processor hardware is not used in idle states, entering them
27 CPU idle time management is an energy-efficiency feature concerned about using
28 the idle states of processors for this purpose.
31 ------------
37 software as individual single-core processors. In other words, a CPU is an
46 Second, if the processor is multi-core, each core in it is able to follow at
56 except for one have been put into idle states at the "core level" and the
[all …]
Dcpufreq_drivers.rst1 .. SPDX-License-Identifier: GPL-2.0
21 there is a different cpu-freq driver for each generation.
37 6th Generation: powernow-k6
39 7th Generation: powernow-k7: Athlon, Duron, Geode.
41 8th Generation: powernow-k8: Athlon, Athlon 64, Opteron, Sempron.
46 BIOS supplied data, for powernow-k7 and for powernow-k8, may be
49 The powernow-k8 driver will attempt to use ACPI if so configured,
51 The powernow-k7 driver will try to use the PSB support first, and
57 ``cpufreq-nforce2``
62 The cpufreq-nforce2 driver changes the FSB on nVidia nForce2 platforms.
[all …]
/Documentation/devicetree/bindings/soc/renesas/
Drenesas,r9a09g057-sys.yaml1 # SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
3 ---
4 $id: http://devicetree.org/schemas/soc/renesas/renesas,r9a09g057-sys.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
7 title: Renesas RZ/V2H(P) System Controller (SYS)
10 - Geert Uytterhoeven <geert+renesas@glider.be>
13 The RZ/V2H(P) SYS (System Controller) controls the overall
15 - Trust zone control
16 - Extend access by specific masters to address beyond 4GB space
17 - GBETH configuration
[all …]
/Documentation/admin-guide/thermal/
Dintel_powerclamp.rst6 - Arjan van de Ven <arjan@linux.intel.com>
7 - Jacob Pan <jacob.jun.pan@linux.intel.com>
12 - Goals and Objectives
15 - Idle Injection
16 - Calibration
19 - Effectiveness and Limitations
20 - Power vs Performance
21 - Scalability
22 - Calibration
23 - Comparison with Alternative Techniques
[all …]
/Documentation/devicetree/bindings/cpufreq/
Dapple,cluster-cpufreq.yaml1 # SPDX-License-Identifier: GPL-2.0-only OR BSD-2-Clause
3 ---
4 $id: http://devicetree.org/schemas/cpufreq/apple,cluster-cpufreq.yaml#
5 $schema: http://devicetree.org/meta-schemas/core.yaml#
10 - Hector Martin <marcan@marcan.st>
13 Apple SoCs (e.g. M1) have a per-cpu-cluster DVFS controller that is part of
15 operating-points-v2 table to define the CPU performance states, with the
16 opp-level property specifying the hardware p-state index for that level.
21 - items:
22 - enum:
[all …]
/Documentation/trace/
Devents-power.rst8 - Power state switch which reports events related to suspend (S-states),
9 cpuidle (C-states) and cpufreq (P-states)
10 - System clock related changes
11 - Power domains related changes and transitions
22 -----------------
24 A 'cpu' event class gathers the CPU-related events: cpuidle and
39 Note: the value of '-1' or '4294967295' for state means an exit from the current state,
46 correctly draw the states diagrams and to calculate accurate statistics etc.
/Documentation/trace/rv/
Ddeterministic_automata.rst10 - *X* is the set of states;
11 - *E* is the finite set of events;
12 - x\ :subscript:`0` is the initial state;
13 - X\ :subscript:`m` (subset of *X*) is the set of marked (or final) states.
14 - *f* : *X* x *E* -> *X* $ is the transition function. It defines the state
22 - *X* = { ``preemptive``, ``non_preemptive``}
23 - *E* = { ``preempt_enable``, ``preempt_disable``, ``sched_waking``}
24 - x\ :subscript:`0` = ``preemptive``
25 - X\ :subscript:`m` = {``preemptive``}
26 - *f* =
[all …]
/Documentation/ABI/testing/
Dusb-charger-uevent2 Date: 2020-01-14
4 Contact: linux-usb@vger.kernel.org
5 Description: There are two USB charger states:
7 - USB_CHARGER_ABSENT
8 - USB_CHARGER_PRESENT
20 https://www.usb.org/document-library/battery-charging-v12-spec-and-adopters-agreement
22 Here are two examples taken using ``udevadm monitor -p`` when
29 MODALIAS=of:Nusbphynop1T(null)Cusb-nop-xceiv
30 OF_COMPATIBLE_0=usb-nop-xceiv
46 MODALIAS=of:Nusbphynop1T(null)Cusb-nop-xceiv
[all …]
Dsysfs-devices-system-cpu2 Date: pre-git history
3 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
18 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
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>
67 /sys/devices/system/cpu/cpu42/node2 -> ../../node/node2
77 Contact: Linux kernel mailing list <linux-kernel@vger.kernel.org>
89 core_siblings_list: human-readable list of the logical CPU
99 thread_siblings_list: human-readable list of cpuX's hardware
[all …]
/Documentation/driver-api/thermal/
Dcpu-idle-cooling.rst1 .. SPDX-License-Identifier: GPL-2.0
8 ----------
26 budget lower than the requested one and under-utilize the CPU, thus
27 losing performance. In other words, one OPP under-utilizes the CPU
33 ----------
58 ---------------
78 |------- -------
81 <------>
82 idle <---------------------->
85 <----------------------------->
[all …]
/Documentation/mm/
Dhwpoison.rst27 Handles page cache pages in various states. The tricky part
41 The code consists of a the high level handler in mm/memory-failure.c,
46 of applications. KVM support requires a recent qemu-kvm release.
109 * madvise(MADV_HWPOISON, ....) (as root) - Poison a page in the
112 * hwpoison-inject module through debugfs ``/sys/kernel/debug/hwpoison/``
114 corrupt-pfn
118 unpoison-pfn
119 Software-unpoison page at PFN echoed into this file. This way
127 corrupt-filter-dev-major, corrupt-filter-dev-minor
129 system defined by block device major/minor. -1U is the
[all …]
/Documentation/virt/kvm/x86/
Dtimekeeping.rst1 .. SPDX-License-Identifier: GPL-2.0
4 Timekeeping Virtualization for X86-Based Architectures
32 information relevant to KVM and hardware-based virtualization.
41 2.1. i8254 - PIT
42 ----------------
46 channels which can be programmed to deliver periodic or one-shot interrupts.
53 The PIT uses I/O ports 0x40 - 0x43. Access to the 16-bit counters is done
59 -------------- ----------------
61 | 1.1932 MHz|---------->| CLOCK OUT | ---------> IRQ 0
63 -------------- | +->| GATE TIMER 0 |
[all …]
/Documentation/admin-guide/device-mapper/
Dsnapshot.rst2 Device-mapper snapshot support
5 Device-mapper allows you, without massive data copying:
7 - To create snapshots of any block device i.e. mountable, saved states of
10 - To create device "forks", i.e. multiple different versions of the
12 - To merge a snapshot of a block device back into the snapshot's origin
16 changed and uses a separate copy-on-write (COW) block device for
24 snapshot, snapshot-origin, and snapshot-merge.
26 - snapshot-origin <origin>
34 - snapshot <origin> <COW device> <persistent?> <chunksize>
45 <persistent?> is P (Persistent) or N (Not persistent - will not survive
[all …]
/Documentation/driver-api/
Dpin-control.rst9 - Enumerating and naming controllable pins
11 - Multiplexing of pins, pads, fingers (etc) see below for details
13 - Configuration of pins, pads, fingers (etc), such as software-controlled
14 biasing and driving mode specific pins, such as pull-up, pull-down, open drain,
17 Top-level interface
22 - A PIN CONTROLLER is a piece of hardware, usually a set of registers, that
26 - PINS are equal to pads, fingers, balls or whatever packaging input or
30 be sparse - i.e. there may be gaps in the space with numbers where no
60 .. code-block:: c
97 See ``arch/arm/mach-ux500/Kconfig`` for an example.
[all …]
/Documentation/admin-guide/
Dkernel-parameters.rst3 The kernel's command-line parameters
12 The kernel parses parameters from the kernel command line up to "``--``";
16 Everything after "``--``" is passed as an argument to init.
32 log_buf_len=1M print-fatal-signals=1
36 log-buf-len=1M print_fatal_signals=1
38 Double-quotes can be used to protect spaces in values, e.g.::
43 ----------
52 <cpu number>-<cpu number>
57 <cpu number>,...,<cpu number>-<cpu number>
63 <cpu number>-<cpu number>:<used size>/<group size>
[all …]
/Documentation/bpf/
Dgraph_ds_impl.rst5 This document describes implementation details of new-style "graph" data
22 ------------
31 no longer relevant. With the introduction of kfuncs, kptrs, and the any-context
35 Two such data structures - linked_list and rbtree - have many verification
44 ------------
47 helper functions - either standard map API helpers like ``bpf_map_update_elem``
48 or map-specific helpers. The new-style graph data structures instead use kfuncs
57 -------
59 The new-style data structures are intrusive and are defined similarly to their
62 .. code-block:: c
[all …]
/Documentation/filesystems/
Dsharedsubtree.rst1 .. SPDX-License-Identifier: GPL-2.0
10 3) Setting mount states
11 4) Use-case
19 -----------
27 It provides the necessary building blocks for features like per-user-namespace
31 -----------
49 mount --make-shared /mnt
51 Note: mount(8) command now supports the --make-shared flag,
57 # mount --bind /mnt /tmp
94 # mount --make-shared /mnt
[all …]
/Documentation/networking/
Dxfrm_device.rst1 .. SPDX-License-Identifier: GPL-2.0
5 XFRM device - offloading the IPsec computations
30 * Kernel and NIC have SA and policy in-sync
31 * NIC handles the SA and policies states
40 reqid 0x07 replay-window 32 \
48 reqid 0x07 replay-window 32 \
53 ip x p add src 14.0.0.70 dst 14.0.0.52 offload packet dev eth4 dir in
98 adapter->netdev->xfrmdev_ops = &ixgbe_xfrmdev_ops;
99 adapter->netdev->features |= NETIF_F_HW_ESP;
100 adapter->netdev->hw_enc_features |= NETIF_F_HW_ESP;
[all …]
/Documentation/networking/device_drivers/hamradio/
Dbaycom.rst1 .. SPDX-License-Identifier: GPL-2.0
41 This driver is work-in-progress.
69 EPP This is a high-speed modem adaptor that connects to an enhanced parallel
90 simple. Once installed, four interfaces named bc{sf,sh,p,e}[0-3] are available.
91 sethdlc from the ax25 utilities may be used to set driver states etc.
110 sethdlc -i bcsf0 -p mode "ser12*" io 0x3f8 irq 4
117 sethdlc -i bcp0 -p mode "picpar" io 0x378
123 The channel access parameters can be set with sethdlc -a or kissparms.
/Documentation/RCU/Design/Requirements/
DRequirements.rst16 ------------
18 Read-copy update (RCU) is a synchronization mechanism that is often used
19 as a replacement for reader-writer locking. RCU is unusual in that
20 updaters do not block readers, which means that RCU's read-side
28 thought of as an informal, high-level specification for RCU. It is
40 #. `Fundamental Non-Requirements`_
42 #. `Quality-of-Implementation Requirements`_
44 #. `Software-Engineering Requirements`_
53 ------------------------
58 #. `Grace-Period Guarantee`_
[all …]
/Documentation/process/
Ddeprecated.rst1 .. SPDX-License-Identifier: GPL-2.0
21 ------------
33 ------------------
35 error condition as gracefully as possible. While the BUG()-family
39 various states been restored?") Very commonly, using BUG() will
42 <https://lore.kernel.org/lkml/CA+55aFy6jNLsywVYdGp83AMrXBo_P-pkjkphPGrO=82SPKCpLQ@mail.gmail.com/>`_
44 <https://lore.kernel.org/lkml/CAHk-=whDHsbK3HTOpTF=ue_o04onRwTEaK_ZoJp_fjbqq4+=Jw@mail.gmail.com/>`…
46 Note that the WARN()-family should only be used for "expected to
48 but undesirable" situations, please use the pr_warn()-family of
54 open-coded arithmetic in allocator arguments
[all …]
/Documentation/scheduler/
Dsched-deadline.rst12 3. Scheduling Real-Time Tasks
18 4.1 System-wide settings
33 system behavior. As for -rt (group) scheduling, it is assumed that root users
50 ------------------
70 with the "traditional" real-time task model (see Section 3) can effectively
76 - Each SCHED_DEADLINE task is characterized by the "runtime",
79 - The state of the task is described by a "scheduling deadline", and
82 - When a SCHED_DEADLINE task wakes up (becomes ready for execution),
86 ---------------------------------- > ---------
87 scheduling deadline - current time period
[all …]

123