| /linux-2.6.39/arch/sparc/kernel/ |
| D | cpu.c | 46 #define CPU(ver, _name) \ macro
60 CPU(0, "Fujitsu MB86900/1A or LSI L64831 SparcKIT-40"),
62 CPU(4, "Fujitsu MB86904"),
63 CPU(5, "Fujitsu TurboSparc MB86907"),
64 CPU(-1, NULL)
80 CPU(0, "LSI Logic Corporation - L64811"),
82 CPU(1, "Cypress/ROSS CY7C601"),
84 CPU(3, "Cypress/ROSS CY7C611"),
86 CPU(0xf, "ROSS HyperSparc RT620"),
87 CPU(0xe, "ROSS HyperSparc RT625 or RT626"),
[all …]
|
| /linux-2.6.39/Documentation/ |
| D | io_ordering.txt | 14 CPU A: spin_lock_irqsave(&dev_lock, flags)
15 CPU A: val = readl(my_status);
16 CPU A: ...
17 CPU A: writel(newval, ring_ptr);
18 CPU A: spin_unlock_irqrestore(&dev_lock, flags)
20 CPU B: spin_lock_irqsave(&dev_lock, flags)
21 CPU B: val = readl(my_status);
22 CPU B: ...
23 CPU B: writel(newval2, ring_ptr);
24 CPU B: spin_unlock_irqrestore(&dev_lock, flags)
[all …]
|
| D | memory-barriers.txt | 29 - CPU memory barriers.
39 (*) Inter-CPU locking barrier effects.
84 | CPU 1 |<----->| Memory |<----->| CPU 2 |
101 Each CPU executes a program that generates memory access operations. In the
102 abstract CPU, memory operation ordering is very relaxed, and a CPU may actually
109 CPU are perceived by the rest of the system as the operations cross the
110 interface between the CPU and rest of the system (the dotted lines).
115 CPU 1 CPU 2
142 Furthermore, the stores committed by a CPU to the memory system may not be
143 perceived by the loads made by another CPU in the same order as the stores were
[all …]
|
| D | workqueue.txt | 38 worker thread per CPU and a single threaded (ST) wq had one worker
41 wq users over the years and with the number of CPU cores continuously
48 worker pool. A MT wq could provide only one execution context per CPU
66 * Use per-CPU unified worker pools shared by all wq to provide
94 The backend is called gcwq. There is one gcwq for each possible CPU
101 things like CPU locality, reentrancy, concurrency limits and more. To
110 CPU the issuer is running on.
118 Each gcwq bound to an actual CPU implements concurrency management by
122 hog a CPU and consume many cycles. That means maintaining just enough
125 CPU, the gcwq doesn't start execution of a new work, but, when the
[all …]
|
| D | cpu-hotplug.txt | 1 CPU hotplug Support in Linux(tm) Kernel
4 CPU Hotplug Core:
24 reporting and correction capabilities in processors. CPU architectures permit
25 partitioning support, where compute resources of a single CPU could be made
28 node insertion and removal require support for CPU hotplug.
31 provisioning reasons, or for RAS purposes to keep an offending CPU off
32 system execution path. Hence the need for CPU hotplug support in the
35 A more novel use of CPU-hotplug support is its use today in suspend
40 General Stuff about CPU Hotplug
74 CPU maps and such
[all …]
|
| D | local_ops.txt | 15 Local atomic operations are meant to provide fast and highly reentrant per CPU
20 Having fast per CPU atomic counters is interesting in many cases : it does not
26 CPU which owns the data. Therefore, care must taken to make sure that only one
27 CPU writes to the local_t data. This is done by using per cpu data and making
29 permitted to read local_t data from any CPU : it will then appear to be written
30 out of order wrt other memory writes by the owner CPU.
51 - _Only_ the CPU owner of these variables must write to them.
52 - This CPU can use local ops from any context (process, irq, softirq, nmi, ...)
56 different CPU between getting the per-cpu variable and doing the
59 taken on a mainline kernel, since they will run on the local CPU with
[all …]
|
| /linux-2.6.39/Documentation/RCU/ |
| D | stallwarn.txt | 1 Using RCU's CPU Stall Detector
4 RCU's CPU stall detector, which detects conditions that unduly delay
11 the beginning of a grace period until it issues an RCU CPU
23 The CPU stall detector tries to make the offending CPU print its
25 However, if the offending CPU does not detect its own stall in
27 some other CPU will complain. This delay is normally set to
30 When a CPU detects that it is stalling, it will print a message similar
33 INFO: rcu_sched_state detected stall on CPU 5 (t=2500 jiffies)
35 This message indicates that CPU 5 detected that it was causing a stall,
37 followed by a stack dump of the offending CPU. On TREE_RCU kernel builds,
[all …]
|
| D | trace.txt | 44 additional section for rcu_preempt. Each section has one line per CPU,
45 or eight for this 8-CPU system. The fields are as follows:
47 o The number at the beginning of each line is the CPU number.
54 o "c" is the count of grace periods that this CPU believes have
56 behind, for example, CPU 4 under "rcu_sched" above, which has
60 o "g" is the count of grace periods that this CPU believes have
62 If the "c" and "g" values are equal, this CPU has already
64 it is aware of, otherwise, the CPU believes that it owes RCU a
67 o "pq" indicates that this CPU has passed through a quiescent state
70 the CPU has passed through a quiescent state, either (1) this
[all …]
|
| /linux-2.6.39/drivers/media/video/cx18/ |
| D | cx18-mailbox.c | 50 API_ENTRY(CPU, CX18_CPU_SET_CHANNEL_TYPE, 0),
51 API_ENTRY(CPU, CX18_EPU_DEBUG, 0),
52 API_ENTRY(CPU, CX18_CREATE_TASK, 0),
53 API_ENTRY(CPU, CX18_DESTROY_TASK, 0),
54 API_ENTRY(CPU, CX18_CPU_CAPTURE_START, API_SLOW),
55 API_ENTRY(CPU, CX18_CPU_CAPTURE_STOP, API_SLOW),
56 API_ENTRY(CPU, CX18_CPU_CAPTURE_PAUSE, 0),
57 API_ENTRY(CPU, CX18_CPU_CAPTURE_RESUME, 0),
58 API_ENTRY(CPU, CX18_CPU_SET_CHANNEL_TYPE, 0),
59 API_ENTRY(CPU, CX18_CPU_SET_STREAM_OUTPUT_TYPE, 0),
[all …]
|
| /linux-2.6.39/Documentation/cpu-freq/ |
| D | cpufreq-stats.txt | 2 CPU frequency and voltage scaling statistics in the Linux(TM) kernel
20 cpufreq-stats is a driver that provides CPU frequency statistics for each CPU.
23 in /sysfs (<sysfs root>/devices/system/cpu/cpuX/cpufreq/stats/) for each CPU.
27 that may be running on your CPU. So, it will work with any cpufreq_driver.
54 this CPU. The cat output will have "<frequency> <time>" pair in each line, which
55 will mean this CPU spent <time> usertime units of time at <frequency>. Output
70 This gives the total number of frequency transitions on this CPU. The cat
80 This will give a fine grained information about all the CPU frequency
104 CPU Frequency scaling --->
105 [*] CPU Frequency scaling
[all …]
|
| D | governors.txt | 1 CPU frequency and voltage scaling code in the Linux(TM) kernel
18 the clock speed, the less power the CPU consumes.
40 cpu frequency scaling algorithms only offer the CPU to be set to one
60 CPU can be set to switch independently | CPU can only be set
87 The CPUfreq governor "performance" sets the CPU statically to the
95 The CPUfreq governor "powersave" sets the CPU statically to the
104 program running with UID "root", to set the CPU to a specific frequency
105 by making a sysfs file "scaling_setspeed" available in the CPU-device
112 The CPUfreq governor "ondemand" sets the CPU depending on the
113 current usage. To do this the CPU must have the capability to
[all …]
|
| D | cpu-drivers.txt | 1 CPU frequency and voltage scaling code in the Linux(TM) kernel
17 the clock speed, the less power the CPU consumes.
24 1.2 Per-CPU Initialization
36 So, you just got a brand-new CPU / chipset with datasheets and want to
37 add cpufreq support for this CPU / chipset? Great. Here are some hints
45 function check whether this kernel runs on the right CPU and the right
55 cpufreq_driver.init - A pointer to the per-CPU initialization
65 cpufreq_driver.exit - A pointer to a per-CPU cleanup function.
67 cpufreq_driver.resume - A pointer to a per-CPU resume function
78 1.2 Per-CPU Initialization
[all …]
|
| D | user-guide.txt | 1 CPU frequency and voltage scaling code in the Linux(TM) kernel
15 the clock speed, the less power the CPU consumes.
32 3. How to change the CPU cpufreq policy and/or speed
113 Some CPU frequency scaling-capable processor switch between various
139 3. How to change the CPU cpufreq policy and/or speed
148 (e.g. /sys/devices/system/cpu/cpu0/cpufreq/ for the first CPU).
154 cpuinfo_transition_latency The time it takes on this CPU to
167 used to set the frequency on this CPU
179 cpuinfo_cur_freq : Current frequency of the CPU as obtained from
181 the CPU actually runs at.
[all …]
|
| /linux-2.6.39/Documentation/ia64/ |
| D | IRQ-redir.txt | 11 IRQ target is one particular CPU and cannot be a mask of several
17 The target CPU has to be specified as a hexadecimal CPU mask. The
18 first non-zero bit is the selected CPU. This format has been kept for
22 interrupts to CPU #3 (logical CPU number) (2^3=0x08):
25 Set the default route for IRQ number 41 to CPU 6 in lowest priority
31 gives the target CPU mask for the specified interrupt vector. If the CPU
41 IO-SAPIC interrupts are initialized with CPU#0 as their default target
48 - maximal if the CPU is going to be switched off.
49 The IRQ is routed to the CPU with lowest XTP register value, the
50 search begins at the default CPU. Therefore most of the interrupts
[all …]
|
| /linux-2.6.39/arch/blackfin/mach-bf548/include/mach/ |
| D | bf548.h | 85 # define CPU "BF542" macro
88 # define CPU "BF544" macro
91 # define CPU "BF547" macro
94 # define CPU "BF548" macro
97 # define CPU "BF549" macro
101 #ifndef CPU
|
| /linux-2.6.39/arch/mips/bcm63xx/ |
| D | Kconfig | 1 menu "CPU support"
5 bool "support 6338 CPU"
12 bool "support 6345 CPU"
17 bool "support 6348 CPU"
21 bool "support 6358 CPU"
|
| /linux-2.6.39/arch/blackfin/mach-bf527/include/mach/ |
| D | bf527.h | 209 #define CPU "BF527" macro
213 #define CPU "BF526" macro
217 #define CPU "BF525" macro
221 #define CPU "BF524" macro
225 #define CPU "BF523" macro
229 #define CPU "BF522" macro
233 #ifndef CPU
|
| /linux-2.6.39/drivers/cpufreq/ |
| D | Kconfig | 2 bool "CPU Frequency scaling"
4 CPU Frequency scaling allows you to change the clock speed of
6 the lower the CPU clock speed, the less power the CPU consumes.
8 Note that this driver doesn't automatically change the CPU
35 tristate "CPU frequency translation statistics"
39 This driver exports CPU frequency statistics information through sysfs
48 bool "CPU frequency translation statistics details"
51 This will show detail CPU frequency translation table in sysfs file
70 the CPU.
79 the CPU.
[all …]
|
| /linux-2.6.39/arch/arm/mach-omap1/ |
| D | Kconfig | 171 comment "OMAP CPU Speed"
183 bool "OMAP ARM 216 MHz CPU (1710 only)"
186 Enable 216 MHz clock for OMAP1710 CPU. If unsure, say N.
189 bool "OMAP ARM 195 MHz CPU"
192 Enable 195MHz clock for OMAP CPU. If unsure, say N.
195 bool "OMAP ARM 192 MHz CPU"
198 Enable 192MHz clock for OMAP CPU. If unsure, say N.
201 bool "OMAP ARM 182 MHz CPU"
204 Enable 182MHz clock for OMAP CPU. If unsure, say N.
207 bool "OMAP ARM 168 MHz CPU"
[all …]
|
| /linux-2.6.39/Documentation/cgroups/ |
| D | cpuacct.txt | 1 CPU Accounting Controller
4 The CPU accounting controller is used to group tasks using cgroups and
5 account the CPU usage of these groups of tasks.
7 The CPU accounting controller supports multi-hierarchy groups. An accounting
8 group accumulates the CPU usage of all of its child groups and the tasks
19 /cgroups/cpuacct.usage gives the CPU time (in nanoseconds) obtained by
20 this group which is essentially the CPU time obtained by all the tasks
30 process (bash) into it. CPU time consumed by this bash and its children
35 CPU time obtained by the cgroup into user and system times. Currently
|
| /linux-2.6.39/arch/mn10300/proc-mn2ws0050/include/proc/ |
| D | smp-regs.h | 31 #define CROSS_GxICR(X, CPU) __SYSREG(0xc4000000 + (X) * 4 + \ argument
32 ((X) >= 64 && (X) < 192) * 0xf00 + ((CPU) << CROSS_ICR_CPU_SHIFT), u16)
33 #define CROSS_GxICR_u8(X, CPU) __SYSREG(0xc4000000 + (X) * 4 + \ argument
34 (((X) >= 64) && ((X) < 192)) * 0xf00 + ((CPU) << CROSS_ICR_CPU_SHIFT), u8)
|
| /linux-2.6.39/Documentation/x86/x86_64/ |
| D | cpu-hotplug-spec | 1 Firmware support for CPU hotplug under Linux/x86-64
4 Linux/x86-64 supports CPU hotplug now. For various reasons Linux wants to
9 In ACPI each CPU needs an LAPIC object in the MADT table (5.2.11.5 in the
13 For CPU hotplug Linux/x86-64 expects now that any possible future hotpluggable
14 CPU is already available in the MADT. If the CPU is not available yet
|
| /linux-2.6.39/Documentation/ABI/testing/ |
| D | sysfs-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.:
44 Description: CPU topology files that describe kernel limits related to
69 Description: Dynamic addition and removal of CPU's. This is not hotplug
70 removal, this is meant complete removal/addition of the CPU
73 probe: writes to this file will dynamically add a CPU to the
74 system. Information written to the file to add CPU's is
77 release: writes to this file dynamically remove a CPU from
78 the system. Information writtento the file to remove CPU's
[all …]
|
| /linux-2.6.39/arch/blackfin/mach-bf537/include/mach/ |
| D | bf537.h | 92 #define CPU "BF537" macro
96 #define CPU "BF536" macro
100 #define CPU "BF534" macro
104 #ifndef CPU
|
| /linux-2.6.39/arch/blackfin/mach-bf518/include/mach/ |
| D | bf518.h | 194 #define CPU "BF518" macro
198 #define CPU "BF516" macro
202 #define CPU "BF514" macro
206 #define CPU "BF512" macro
210 #ifndef CPU
|