Home
last modified time | relevance | path

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

12

/tools/testing/selftests/tc-testing/bpf/
DMakefile15 CPU ?= probe macro
17 CPU ?= generic macro
30 $(LLC) -march=bpf -mcpu=$(CPU) $(LLC_FLAGS) -filetype=obj -o $@
/tools/power/cpupower/po/
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 …]
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 …]
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 …]
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/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/perf/tests/
Dhists_output.c121 #define CPU(he) (he->cpu) macro
269 CPU(he) == 1 && PID(he) == 100 && he->stat.period == 300); in test2()
274 CPU(he) == 0 && PID(he) == 100 && he->stat.period == 100); in test2()
505 CPU(he) == 0 && PID(he) == 100 && in test5()
512 CPU(he) == 2 && PID(he) == 200 && in test5()
519 CPU(he) == 1 && PID(he) == 300 && in test5()
526 CPU(he) == 0 && PID(he) == 300 && in test5()
533 CPU(he) == 3 && PID(he) == 300 && in test5()
540 CPU(he) == 1 && PID(he) == 100 && in test5()
547 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/memory-model/Documentation/
Dexplanation.txt103 is full. Running concurrently on a different CPU might be a part of
132 CPU and P1() represents the read() routine running on another. The
140 This pattern of memory accesses, where one CPU stores values to two
141 shared memory locations and another CPU loads from those locations in
184 if each CPU executed its instructions in order but with unspecified
188 program source for each CPU. The model says that the value obtained
190 store to the same memory location, from any CPU.
222 each CPU stores to its own shared location and then loads from the
223 other CPU's location:
313 private memory or CPU registers are not of central interest to the
[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 …]
/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
115 If a CPU is not able to count the selected event, then the system call
118 More hw_event_types are supported as well, but they are CPU-specific
206 on the CPU if at all possible. It only applies to hardware counters
208 CPU (e.g. because there are not enough hardware counters or because of
214 is on the CPU, it should be the only group using the CPU's counters.
217 advanced features of the CPU's Performance Monitor Unit (PMU) that are
223 CPU is in user, kernel and/or hypervisor mode.
248 The 'cpu' parameter allows a counter to be made specific to a CPU:
[all …]
/tools/testing/selftests/rcutorture/configs/lock/
Dver_functions.sh16 echo CPU-hotplug kernel, adding locktorture onoff. 1>&2
/tools/perf/Documentation/
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.
136 Show visual aid for sched switches by CPU: 'i' marks idle time,
Dperf-timechart.txt19 and CPU events (task switches, running times, CPU power states, etc),
46 Only output the CPU power section of the diagram
Dperf-stat.txt271 Print top down level 1 metrics if supported by the CPU. This allows to
272 determine bottle necks in the CPU pipeline for CPU bound workloads,
276 Frontend bound means that the CPU cannot fetch and decode instructions fast
278 neck. Bad Speculation means that the CPU wasted cycles due to branch
279 mispredictions and similar issues. Retiring means that the CPU computed without
281 if the workload is actually bound by the CPU and not by something else.
287 CPU thread. Per core mode is automatically enabled
376 - optional CPU, core, or socket identifier
Dperf.txt44 covers hardware level (CPU/PMU, Performance Monitoring Unit) features
/tools/testing/selftests/rcutorture/configs/rcu/
Dver_functions.sh28 echo CPU-hotplug kernel, adding rcutorture onoff. 1>&2
/tools/perf/tests/attr/
Dtest-record-C09 # no enable on exec for CPU attached
/tools/testing/selftests/bpf/
DMakefile134 CPU ?= probe macro
136 CPU ?= generic macro
216 $(LLC) -march=bpf -mattr=+alu32 -mcpu=$(CPU) $(LLC_FLAGS) \
255 $(LLC) -march=bpf -mcpu=$(CPU) $(LLC_FLAGS) -filetype=obj -o $@
263 $(LLC) -march=bpf -mcpu=$(CPU) $(LLC_FLAGS) -filetype=obj -o $@
/tools/power/cpupower/
DToDo3 - Use bitmask functions to parse CPU topology more robust
/tools/memory-model/litmus-tests/
DMP+porevlocks.litmus9 * given lock), a CPU is not only guaranteed to see the accesses that other
DMP+polocks.litmus9 * given lock), a CPU is not only guaranteed to see the accesses that other
/tools/perf/arch/arm64/util/
Darm-spe.c123 perf_evsel__set_sample_bit(arm_spe_evsel, CPU); in arm_spe_recording_options()
138 perf_evsel__set_sample_bit(tracking_evsel, CPU); in arm_spe_recording_options()
/tools/testing/selftests/netfilter/
Dnft_trans_stress.sh52 lscpu | grep ^CPU\(s\): | ( read cpu cpunum ;

12