Home
last modified time | relevance | path

Searched refs:CPU (Results 1 – 25 of 86) sorted by relevance

1234

/tools/memory-model/Documentation/
Dglossary.txt30 load before later memory references running on that same CPU.
42 Coherence (co): When one CPU's store to a given variable overwrites
43 either the value from another CPU's store or some later value,
44 there is said to be a coherence link from the second CPU to
47 It is also possible to have a coherence link within a CPU, which
73 In a cycle, each CPU's ordering interacts with that of the next:
75 CPU 0 CPU 1 CPU 2
80 CPU 0's smp_mb() interacts with that of CPU 1, which interacts
81 with that of CPU 2, which in turn interacts with that of CPU 0
105 From-Reads (fr): When one CPU's store to a given variable happened
[all …]
Drecipes.txt15 there is only one CPU or only one memory location is accessed, and the
19 Single CPU or single memory location
22 If there is only one CPU on the one hand or only one variable
50 being updated by some other CPU, for example, while
65 about it too hard. And the basic rule is indeed quite simple: Any CPU that
67 CPU before it released that same lock. Note that this statement is a bit
68 stronger than "Any CPU holding a given lock sees all changes made by any
69 CPU during the time that CPU was holding this same lock". For example,
203 The MP pattern has one CPU execute a pair of stores to a pair of variables
204 and another CPU execute a pair of loads from this same pair of variables,
[all …]
Dexplanation.txt104 is full. Running concurrently on a different CPU might be a part of
133 CPU and P1() represents the read() routine running on another. The
141 This pattern of memory accesses, where one CPU stores values to two
142 shared memory locations and another CPU loads from those locations in
185 if each CPU executed its instructions in order but with unspecified
189 program source for each CPU. The model says that the value obtained
191 store to the same memory location, from any CPU.
223 each CPU stores to its own shared location and then loads from the
224 other CPU's location:
314 private memory or CPU registers are not of central interest to the
[all …]
Dlocking.txt5 CPU holding a given lock sees any changes previously seen or made by any
6 CPU before it previously released that same lock. This last sentence
18 Any CPU holding a given lock sees any changes previously seen
19 or made by any CPU before it previously released that same lock.
21 Note that this statement is a bit stronger than "Any CPU holding a
22 given lock sees all changes made by any CPU during the time that CPU was
53 The converse to the basic rule also holds: Any CPU holding a given
54 lock will not see any changes that will be made by any CPU after it
/tools/power/cpupower/po/
Dka.po110 msgid "\t -t: show CPU topology/hierarchy\n"
111 msgstr "\t -t: CPU -ის ტოპოლოგიის/იერარქიის ჩვენება\n"
115 msgid "\t -l: list available CPU sleep monitors (for use with -m)\n"
117 "\t -l: CPU-ის ძილის მონიტორების სიის გამოტანა (განკუთვნილია -m -სთან ერთად "
122 msgid "\t -m: show specific CPU sleep monitors only (in same order)\n"
124 "\t -m: მხოლოდ მითითებული CPU-ის ძილის მონიტორების ჩვენება (იგივე "
241 msgstr "CPU-ების სიის დამუშავების შეცდომა\n"
252 "CPU-ების (%s: %s) რაოდენობის მიღების შეცდომა. ჩაითვლება, რომ უდრის 1-ს\n"
257 " minimum CPU frequency - maximum CPU frequency - governor\n"
259 " CPU-ის მინიმალური სიხშირე - CPU-ის მაქსიმალური სიხშირე - "
[all …]
Dit.po103 msgid "\t -t: show CPU topology/hierarchy\n"
108 msgid "\t -l: list available CPU sleep monitors (for use with -m)\n"
113 msgid "\t -m: show specific CPU sleep monitors only (in same order)\n"
230 msgstr "Impossibile determinare il numero di CPU (%s: %s), assumo sia 1\n"
235 " minimum CPU frequency - maximum CPU frequency - governor\n"
237 " frequenza minima CPU - frequenza massima CPU - gestore\n"
241 msgid "Error while evaluating Boost Capabilities on CPU %d -- are you root?\n"
294 msgid " no or unknown cpufreq driver is active on this CPU\n"
295 msgstr " nessun modulo o modulo cpufreq sconosciuto per questa CPU\n"
305 msgstr " CPU che operano alla stessa frequenza hardware: "
[all …]
Dfr.po103 msgid "\t -t: show CPU topology/hierarchy\n"
108 msgid "\t -l: list available CPU sleep monitors (for use with -m)\n"
113 msgid "\t -m: show specific CPU sleep monitors only (in same order)\n"
235 " minimum CPU frequency - maximum CPU frequency - governor\n"
237 " Fréquence CPU minimale - Fréquence CPU maximale - régulateur\n"
241 msgid "Error while evaluating Boost Capabilities on CPU %d -- are you root?\n"
294 msgid " no or unknown cpufreq driver is active on this CPU\n"
295 msgstr " pas de pilotes cpufreq reconnu pour ce CPU\n"
353 msgid " current CPU frequency is "
354 msgstr " la fréquence actuelle de ce CPU est "
[all …]
Dcs.po106 msgid "\t -t: show CPU topology/hierarchy\n"
111 msgid "\t -l: list available CPU sleep monitors (for use with -m)\n"
116 msgid "\t -m: show specific CPU sleep monitors only (in same order)\n"
235 msgstr "Nelze zjistit počet CPU (%s: %s), předpokládá se 1.\n"
240 " minimum CPU frequency - maximum CPU frequency - governor\n"
242 " minimální frekvence CPU - maximální frekvence CPU - regulátor\n"
246 msgid "Error while evaluating Boost Capabilities on CPU %d -- are you root?\n"
299 msgid " no or unknown cpufreq driver is active on this CPU\n"
300 msgstr " pro tento CPU není aktivní žádný známý ovladač cpufreq\n"
310 msgstr " CPU, které musí měnit frekvenci zároveň: "
[all …]
Dpt.po101 msgid "\t -t: show CPU topology/hierarchy\n"
106 msgid "\t -l: list available CPU sleep monitors (for use with -m)\n"
111 msgid "\t -m: show specific CPU sleep monitors only (in same order)\n"
233 " minimum CPU frequency - maximum CPU frequency - governor\n"
235 " frequência mínina do CPU - frequência máxima do CPU - "
240 msgid "Error while evaluating Boost Capabilities on CPU %d -- are you root?\n"
293 msgid " no or unknown cpufreq driver is active on this CPU\n"
294 msgstr " nenhum ou driver do cpufreq deconhecido está ativo nesse CPU\n"
352 msgid " current CPU frequency is "
353 msgstr " frequência atual do CPU é "
[all …]
Dde.po107 msgid "\t -t: show CPU topology/hierarchy\n"
108 msgstr "\t -t: CPU-Topologie/Hierarchie anzeigen\n"
112 msgid "\t -l: list available CPU sleep monitors (for use with -m)\n"
114 "\t -l: verfügbare CPU-Schlafwächter auflisten (für Verwendung mit -m)\n"
118 msgid "\t -m: show specific CPU sleep monitors only (in same order)\n"
120 "\t -m: spezifische CPU-Schlafwächter anzeigen (in gleicher Reihenfolge)\n"
232 msgstr "Fehler beim Parsen der CPU-Liste\n"
249 " minimum CPU frequency - maximum CPU frequency - governor\n"
250 msgstr " minimale CPU-Frequenz - maximale CPU-Frequenz - Regler\n"
254 msgid "Error while evaluating Boost Capabilities on CPU %d -- are you root?\n"
[all …]
/tools/testing/selftests/tc-testing/
DMakefile13 CPU ?= probe macro
15 CPU ?= generic macro
28 $(LLC) -march=bpf -mcpu=$(CPU) $(LLC_FLAGS) -filetype=obj -o $@
/tools/perf/pmu-events/
DREADME14 - The CSV file that maps a specific CPU to its set of PMU events is to
25 The PMU events supported by a CPU model are expected to grouped into topics
30 All the topic JSON files for a CPU model/family should be in a separate
31 sub directory. Thus for the Silvermont X86 CPU:
37 The JSONs folder for a CPU model/family may be placed in the root arch
61 - A 'mapping table' that maps each CPU of the architecture, to its
86 3. _All_ known CPU tables for architecture are included in the perf
89 At run time, perf determines the actual CPU it is running on, finds the
102 The mapfile enables multiple CPU models to share a single set of PMU events.
126 to identify CPU (and associate it with a set of PMU events
[all …]
/tools/testing/selftests/sgx/
Dtest_encl_bootstrap.S13 .fill 1, 8, 0 # STATE (set by CPU)
16 .fill 1, 4, 0 # CSSA (set by CPU)
27 .fill 1, 8, 0 # STATE (set by CPU)
30 .fill 1, 4, 0 # CSSA (set by CPU)
/tools/memory-model/litmus-tests/
DMP+unlocklockonceonce+fencermbonceonce.litmus6 * If two locked critical sections execute on the same CPU, stores in the
7 * first must propagate to each CPU before stores in the second do, even if
DLB+unlocklockonceonce+poacquireonce.litmus6 * If two locked critical sections execute on the same CPU, all accesses
10 * the viewpoint of another CPU (the kind of reordering allowed by TSO).
/tools/testing/selftests/rcutorture/bin/
Dkvm-test-1-run-batch.sh63 print "echo No CPU-affinity information, so no taskset command.";
69 print "echo " scenario ": Bogus CPU-affinity information, so no taskset command.";
/tools/perf/tests/
Dhists_output.c134 #define CPU(he) (he->cpu) macro
282 CPU(he) == 1 && PID(he) == 100 && he->stat.period == 300); in test2()
287 CPU(he) == 0 && PID(he) == 100 && he->stat.period == 100); in test2()
518 CPU(he) == 0 && PID(he) == 100 && in test5()
525 CPU(he) == 2 && PID(he) == 200 && in test5()
532 CPU(he) == 1 && PID(he) == 300 && in test5()
539 CPU(he) == 0 && PID(he) == 300 && in test5()
546 CPU(he) == 3 && PID(he) == 300 && in test5()
553 CPU(he) == 1 && PID(he) == 100 && in test5()
560 CPU(he) == 2 && PID(he) == 100 && in test5()
[all …]
/tools/power/cpupower/bench/
DREADME-BENCH9 - Identify average reaction time of a governor to CPU load changes
34 You can specify load (100% CPU load) and sleep (0% CPU load) times in us which
55 First it is calibrated how long a specific CPU intensive calculation
69 100% CPU load (load) | 0 % CPU load (sleep) | round
113 -c, --cpu=<unsigned int> CPU Number to use, starting at 0
/tools/perf/Documentation/
Dperf-intel-pt.txt140 Dump all instructions in time range on CPU 1.
200 no more than n samples for a CPU are displayed in a row. 'n' defaults to 4.
291 sample_type IP|TID|TIME|CPU|IDENTIFIER
418 MTC and TSC packets. A CYC packet contains the number of CPU
442 The cyc_thresh value represents the minimum number of CPU cycles
444 number of CPU cycles is:
448 e.g. value 4 means 8 CPU cycles must pass before a CYC packet
450 packet is sent, not at, e.g. every 8 CPU cycles.
489 changes to the CPU C-state.
819 sample_type IP|TID|TIME|CPU|IDENTIFIER
[all …]
Dperf-sched.txt29 threads can then replay the timings (CPU runtime and sleep patterns)
36 are running on a CPU. A '*' denotes the CPU that had the event, and
37 a dot signals an idle CPU.
115 Only show events for the given CPU(s) (comma separated list).
140 Show visual aid for sched switches by CPU: 'i' marks idle time,
/tools/perf/
Ddesign.txt10 thus be used to profile the code that runs on that CPU.
13 hardware capabilities. It provides per task and per CPU counters, counter
118 If a CPU is not able to count the selected event, then the system call
121 More hw_event_types are supported as well, but they are CPU-specific
209 on the CPU if at all possible. It only applies to hardware counters
211 CPU (e.g. because there are not enough hardware counters or because of
217 is on the CPU, it should be the only group using the CPU's counters.
220 advanced features of the CPU's Performance Monitor Unit (PMU) that are
226 CPU is in user, kernel and/or hypervisor mode.
251 The 'cpu' parameter allows a counter to be made specific to a CPU:
[all …]
/tools/testing/selftests/cgroup/
Dtest_cpuset_prs.sh323 CPU=${1%-*}
325 CPUFILE=//sys/devices/system/cpu/cpu${CPU}/online
328 OFFLINE_CPUS="$OFFLINE_CPUS $CPU"
331 OFFLINE_CPUS=$(echo $CPU $CPU $OFFLINE_CPUS | fmt -1 |\
586 echo "Test $TEST[$I] failed effective CPU check!"
/tools/testing/selftests/rcutorture/configs/scf/
Dver_functions.sh16 echo CPU-hotplug kernel, adding scftorture onoff. 1>&2
/tools/testing/selftests/rcutorture/configs/lock/
Dver_functions.sh16 echo CPU-hotplug kernel, adding locktorture onoff. 1>&2
/tools/testing/selftests/rcutorture/configs/rcu/
Dver_functions.sh28 echo CPU-hotplug kernel, adding rcutorture onoff. 1>&2

1234