Home
last modified time | relevance | path

Searched full:cpu (Results 1 – 25 of 823) sorted by relevance

12345678910>>...33

/Documentation/devicetree/bindings/cpu/
Dcpu-topology.txt2 CPU topology binding description
20 For instance in a system where CPUs support SMT, "cpu" nodes represent all
22 In systems where SMT is not supported "cpu" nodes represent all cores present
25 CPU topology bindings allow one to associate cpu nodes with hierarchical groups
29 Currently, only ARM/RISC-V intend to use this cpu topology binding but it may be
32 The cpu nodes, as per bindings defined in [4], represent the devices that
35 A topology description containing phandles to cpu nodes that are not compliant
39 2 - cpu-map node
42 The ARM/RISC-V CPU topology is defined within the cpu-map node, which is a direct
46 - cpu-map node
[all …]
/Documentation/ABI/testing/
Dsysfs-devices-system-cpu1 What: /sys/devices/system/cpu/
5 A collection of both global and individual CPU attributes
7 Individual CPU attributes are contained in subdirectories
8 named by the kernel's logical CPU number, e.g.:
10 /sys/devices/system/cpu/cpu#/
12 What: /sys/devices/system/cpu/kernel_max
13 /sys/devices/system/cpu/offline
14 /sys/devices/system/cpu/online
15 /sys/devices/system/cpu/possible
16 /sys/devices/system/cpu/present
[all …]
/Documentation/translations/zh_CN/
Dio_ordering.txt35 CPU A: spin_lock_irqsave(&dev_lock, flags)
36 CPU A: val = readl(my_status);
37 CPU A: ...
38 CPU A: writel(newval, ring_ptr);
39 CPU A: spin_unlock_irqrestore(&dev_lock, flags)
41 CPU B: spin_lock_irqsave(&dev_lock, flags)
42 CPU B: val = readl(my_status);
43 CPU B: ...
44 CPU B: writel(newval2, ring_ptr);
45 CPU B: spin_unlock_irqrestore(&dev_lock, flags)
[all …]
/Documentation/
Dio_ordering.txt18 CPU A: spin_lock_irqsave(&dev_lock, flags)
19 CPU A: val = readl(my_status);
20 CPU A: ...
21 CPU A: writel(newval, ring_ptr);
22 CPU A: spin_unlock_irqrestore(&dev_lock, flags)
24 CPU B: spin_lock_irqsave(&dev_lock, flags)
25 CPU B: val = readl(my_status);
26 CPU B: ...
27 CPU B: writel(newval2, ring_ptr);
28 CPU B: spin_unlock_irqrestore(&dev_lock, flags)
[all …]
Dthis_cpu_ops.txt8 this_cpu operations are a way of optimizing access to per cpu
11 the cpu permanently stored the beginning of the per cpu area for a
14 this_cpu operations add a per cpu variable offset to the processor
15 specific per cpu base and encode that operation in the instruction
16 operating on the per cpu variable.
32 synchronization is not necessary since we are dealing with per cpu
37 Please note that accesses by remote processors to a per cpu area are
69 per cpu area. It is then possible to simply use the segment override
70 to relocate a per cpu relative address to the proper per cpu area for
71 the processor. So the relocation to the per cpu base is encoded in the
[all …]
/Documentation/scheduler/
Dsched-bwc.rst5 [ This document only discusses CPU bandwidth control for SCHED_NORMAL.
9 specification of the maximum CPU bandwidth available to a group or hierarchy.
13 microseconds of CPU time. That quota is assigned to per-cpu run queues in
21 is transferred to cpu-local "silos" on a demand basis. The amount transferred
26 Quota and period are managed within the cpu subsystem via cgroupfs.
28 cpu.cfs_quota_us: the total available run-time within a period (in microseconds)
29 cpu.cfs_period_us: the length of a period (in microseconds)
30 cpu.stat: exports throttling statistics [explained further below]
34 cpu.cfs_period_us=100ms
35 cpu.cfs_quota=-1
[all …]
/Documentation/devicetree/bindings/arm/
Dcpu-capacity.txt15 2 - CPU capacity definition
18 CPU capacity is a number that provides the scheduler information about CPUs
25 CPU capacities are obtained by running a suitable benchmark. This binding makes
29 * A "single-threaded" or CPU affine benchmark
30 * Divided by the running frequency of the CPU executing the benchmark
31 * Not subject to dynamic frequency scaling of the CPU
36 CPU capacities are obtained by running the Dhrystone benchmark on each CPU at
46 capacity-dmips-mhz is an optional cpu node [1] property: u32 value
47 representing CPU capacity expressed in normalized DMIPS/MHz. At boot time, the
48 maximum frequency available to the cpu is then used to calculate the capacity
[all …]
Dcpus.yaml14 the "cpus" node, which in turn contains a number of subnodes (ie "cpu")
15 defining properties for every cpu.
17 Bindings for CPU nodes follow the Devicetree Specification, available from:
34 cpus and cpu node bindings definition
38 requires the cpus and cpu nodes to be present and contain the properties
55 bits [11:0] in CPU ID register.
60 required and matches the CPU MPIDR[23:0] register
181 - brcm,bcm11351-cpu-method
204 cpu-release-addr:
214 cpu-idle-states:
[all …]
Didle-states.txt11 wfi to power gating) according to OS PM policies. The CPU states representing
17 power states an ARM CPU can be put into are identified by the following list:
25 The power states described in the SBSA document define the basic CPU states on
46 The following diagram depicts the CPU execution phases and related timing
59 Diagram 1: CPU idle state execution phases
61 EXEC: Normal CPU execution.
66 (i.e. less than the ENTRY + EXIT duration). If aborted, CPU
76 EXIT: Period during which the CPU is brought back to operational
86 CPU being able to execute normal code again. If not specified, this is assumed
91 An idle CPU requires the expected min-residency time to select the most
[all …]
Dcoresight-cpu-debug.txt1 * CoreSight CPU Debug Component:
3 CoreSight CPU debug component are compliant with the ARMv8 architecture
7 and eventually the debug module connects with CPU for debugging. And the
9 to sample CPU program counter, secure state and exception level, etc;
10 usually every CPU has one dedicated debug module to be connected.
14 - compatible : should be "arm,coresight-cpu-debug"; supplemented with
26 processor core is clocked by the internal CPU clock, so it
27 is enabled with CPU clock by default.
29 - cpu : the CPU phandle the debug module is affined to. Do not assume it
38 constrain idle states to ensure registers in the CPU power
[all …]
/Documentation/x86/
Dtopology.rst75 A per-CPU variable containing:
105 CPU.
143 The alternative Linux CPU enumeration depends on how the BIOS enumerates the
145 That has the "advantage" that the logical Linux CPU numbers of threads 0 stay
151 [package 0] -> [core 0] -> [thread 0] -> Linux CPU 0
157 [package 0] -> [core 0] -> [thread 0] -> Linux CPU 0
158 -> [core 1] -> [thread 0] -> Linux CPU 1
162 [package 0] -> [core 0] -> [thread 0] -> Linux CPU 0
163 -> [thread 1] -> Linux CPU 1
164 -> [core 1] -> [thread 0] -> Linux CPU 2
[all …]
/Documentation/devicetree/bindings/cpufreq/
Dbrcm,stb-avs-cpu-freq.txt4 A total of three DT nodes are required. One node (brcm,avs-cpu-data-mem)
5 references the mailbox register used to communicate with the AVS CPU[1]. The
6 second node (brcm,avs-cpu-l2-intr) is required to trigger an interrupt on
7 the AVS CPU. The interrupt tells the AVS CPU that it needs to process a
8 command sent to it by a driver. Interrupting the AVS CPU is mandatory for
12 so a driver can react to interrupts generated by the AVS CPU whenever a command
15 [1] The AVS CPU is an independent co-processor that runs proprietary
22 Node brcm,avs-cpu-data-mem
26 - compatible: must include: brcm,avs-cpu-data-mem and
27 should include: one of brcm,bcm7271-avs-cpu-data-mem or
[all …]
Dcpufreq-mediatek.txt7 "cpu" - The multiplexer for clock input of CPU cluster.
8 "intermediate" - A parent of "cpu" clock which is used as "intermediate" clock
9 source (usually MAINPLL) when the original CPU PLL is under
15 - proc-supply: Regulator for Vproc of CPU cluster.
18 - sram-supply: Regulator for Vsram of CPU cluster. When present, the cpufreq driver
59 cpu0: cpu@0 {
60 device_type = "cpu";
65 clock-names = "cpu", "intermediate";
69 cpu@1 {
70 device_type = "cpu";
[all …]
/Documentation/core-api/
Dcpu_hotplug.rst2 CPU hotplug in the Kernel
18 insertion and removal require support for CPU hotplug.
21 provisioning reasons, or for RAS purposes to keep an offending CPU off
22 system execution path. Hence the need for CPU hotplug support in the
25 A more novel use of CPU-hotplug support is its use today in suspend resume
65 CPU maps
78 after a CPU is available for kernel scheduling and ready to receive
79 interrupts from devices. Its cleared when a CPU is brought down using
81 migrated to another target CPU.
91 You really don't need to manipulate any of the system CPU maps. They should
[all …]
/Documentation/RCU/
Dstallwarn.txt1 Using RCU's CPU Stall Detector
3 This document first discusses what sorts of issues RCU's CPU stall
9 What Causes RCU CPU Stall Warnings?
11 So your kernel printed an RCU CPU stall warning. The next question is
12 "What caused it?" The following problems can result in RCU CPU stall
15 o A CPU looping in an RCU read-side critical section.
17 o A CPU looping with interrupts disabled.
19 o A CPU looping with preemption disabled.
21 o A CPU looping with bottom halves disabled.
23 o For !CONFIG_PREEMPT kernels, a CPU looping anywhere in the kernel
[all …]
/Documentation/admin-guide/
Dkernel-per-CPU-kthreads.rst2 Reducing OS jitter due to per-cpu kthreads
5 This document lists per-CPU kthreads in the Linux kernel and presents
6 options to control their OS jitter. Note that non-per-CPU kthreads are
7 not listed here. To reduce OS jitter from non-per-CPU kthreads, bind
8 them to a "housekeeping" CPU dedicated to such work.
23 - /sys/devices/system/cpu/cpuN/online: Control CPU N's hotplug state,
26 - In order to locate kernel-generated OS jitter on CPU N:
46 that does not require per-CPU kthreads. This will prevent these
52 3. Rework the eHCA driver so that its per-CPU kthreads are
65 some other CPU.
[all …]
/Documentation/power/
Dsuspend-and-cpuhotplug.rst2 Interaction of Suspend code (S3) with the CPU hotplug infrastructure
8 I. Differences between CPU hotplug and Suspend-to-RAM
11 How does the regular CPU hotplug code differ from how the Suspend-to-RAM
17 interactions involving the freezer and CPU hotplug and also tries to explain
21 What happens when regular CPU hotplug and Suspend-to-RAM race with each other
66 Common | before taking down the CPU |
79 Disable regular cpu hotplug
99 | Decrease cpu_hotplug_disabled, thereby enabling regular cpu hotplug
117 Regular CPU hotplug call path
121 /sys/devices/system/cpu/cpu*/online
[all …]
/Documentation/devicetree/bindings/arm/cpu-enable-method/
Dal,alpine-smp2 Secondary CPU enable-method "al,alpine-smp" binding
17 "al,alpine-cpu-resume" and "al,alpine-nb-service".
20 * Alpine CPU resume registers
22 The CPU resume register are used to define required resume address after
26 - compatible : Should contain "al,alpine-cpu-resume".
32 The System-Fabric Service Registers allow various operation on CPU and
47 cpu@0 {
49 device_type = "cpu";
53 cpu@1 {
55 device_type = "cpu";
[all …]
/Documentation/vm/
Dmmu_notifier.rst10 For secondary TLB (non CPU TLB) like IOMMU TLB or device TLB (when device use
11 thing like ATS/PASID to get the IOMMU to walk the CPU page table to access a
41 CPU-thread-0 {try to write to addrA}
42 CPU-thread-1 {try to write to addrB}
43 CPU-thread-2 {}
44 CPU-thread-3 {}
48 CPU-thread-0 {COW_step0: {mmu_notifier_invalidate_range_start(addrA)}}
49 CPU-thread-1 {COW_step0: {mmu_notifier_invalidate_range_start(addrB)}}
50 CPU-thread-2 {}
51 CPU-thread-3 {}
[all …]
/Documentation/trace/
Dcoresight-cpu-debug.rst2 Coresight CPU Debug Module
11 Coresight CPU debug module is defined in ARMv8-a architecture reference manual
12 (ARM DDI 0487A.k) Chapter 'Part H: External debug', the CPU can integrate
20 to sample CPU program counter, secure state and exception level, etc; usually
21 every CPU has one dedicated debug module to be connected. Based on self-hosted
24 will dump related registers for every CPU; finally this is good for assistant
43 - The driver supports a CPU running in either AArch64 or AArch32 mode. The
54 instruction set state". For ARMv7-a, the driver checks furthermore if CPU
61 state". So on ARMv8 if EDDEVID1.PCSROffset is 0b0010 and the CPU operates
62 in AArch32 state, EDPCSR is not sampled; when the CPU operates in AArch64
[all …]
/Documentation/arm/
Dcluster-pm-race-avoidance.rst5 This file documents the algorithm which is used to coordinate CPU and
48 Each cluster and CPU is assigned a state, as follows:
67 The CPU or cluster is not coherent, and is either powered off or
71 The CPU or cluster has committed to moving to the UP state.
76 The CPU or cluster is active and coherent at the hardware
77 level. A CPU in this state is not necessarily being used
81 The CPU or cluster has committed to moving to the DOWN
86 Each CPU has one of these states assigned to it at any point in time.
87 The CPU states are described in the "CPU state" section, below.
95 To help distinguish the CPU states from cluster states in this
[all …]
/Documentation/networking/
Dscaling.rst60 for each CPU if the device supports enough queues, or otherwise at least
77 this to notify a CPU when new packets arrive on the given queue. The
79 that can route each interrupt to a particular CPU. The active mapping
81 an IRQ may be handled on any CPU. Because a non-negligible part of packet
98 receive queue overflows due to a saturated CPU, because in default
102 Per-cpu load can be observed using the mpstat utility, but note that on
104 a separate CPU. For interrupt handling, HT has shown no benefit in
105 initial tests, so limit the number of queues to the number of CPU cores
114 Whereas RSS selects the queue and hence CPU that will run the hardware
115 interrupt handler, RPS selects the CPU to perform protocol processing
[all …]
/Documentation/devicetree/bindings/arm/bcm/
Dbrcm,nsp-cpu-method.txt1 Broadcom Northstar Plus SoC CPU Enable Method
4 CPU in the following Broadcom SoCs:
8 properties in the corresponding secondary "cpu" device tree node:
14 entry point for a secondary CPU. This entry is cpu node specific
15 and should be added per cpu. E.g., in case of NSP (BCM58625) which
16 is a dual core CPU SoC, this entry should be added to cpu1 node.
24 cpu0: cpu@0 {
25 device_type = "cpu";
31 cpu1: cpu@1 {
32 device_type = "cpu";
Dbrcm,bcm11351-cpu-method.txt1 Broadcom Kona Family CPU Enable Method
8 properties in the "cpu" device tree node:
9 - enable-method = "brcm,bcm11351-cpu-method";
14 code release a secondary CPU. The value written to the register is
15 formed by encoding the target CPU id into the low bits of the
23 cpu0: cpu@0 {
24 device_type = "cpu";
29 cpu1: cpu@1 {
30 device_type = "cpu";
33 enable-method = "brcm,bcm11351-cpu-method";
/Documentation/devicetree/bindings/csky/
Dcpus.txt2 C-SKY CPU Bindings
6 the "cpus" node, which in turn contains a number of subnodes (ie "cpu")
7 defining properties for every cpu.
13 cpus and cpu node bindings definition
18 Description: Container of cpu nodes
33 - cpu node
42 Definition: must be "cpu"
46 Definition: CPU index
62 cpu@0 {
63 device_type = "cpu";
[all …]

12345678910>>...33