| /tools/testing/selftests/drivers/net/ |
| A D | netcons_sysdata.sh | 111 if ! grep -q "cpu=${CPU}\+" "${OUTPUT_FILE}"; then
112 echo "FAIL: 'cpu=${CPU}' not found in ${OUTPUT_FILE}" >&2
198 taskset -c "${CPU}" echo "${MSG}: ${TARGET}" > /dev/kmsg
229 CPU=$((RANDOM % $(nproc)))
231 MSG="Test #1 from CPU${CPU}"
249 CPU=$((RANDOM % $(nproc)))
251 MSG="Test #2 from CPU${CPU}"
261 CPU=$((RANDOM % $(nproc)))
263 MSG="Test #3 from CPU${CPU}"
|
| /tools/power/cpupower/po/ |
| A D | zh_CN.po | 245 " minimum CPU frequency - maximum CPU frequency - governor\n"
246 msgstr "最低 CPU 频率 - 最高 CPU 频率 - 调速器\n"
363 msgstr " 当前CPU频率是"
535 msgstr "分析 CPU %d：\n"
596 " except the -c CPU, --cpu CPU parameter\n"
602 " 除了 -c CPU、--cpu CPU 参数\n"
654 msgstr "设置CPU：%d\n"
931 #~ " -c CPU, --cpu CPU CPU number which information shall be determined "
934 #~ " -c CPU, --cpu CPU Numéro du CPU pour lequel l'information sera "
938 #~ " -c CPU, --cpu CPU number of CPU where cpufreq settings shall be "
[all …]
|
| A D | ka.po | 257 " minimum CPU frequency - maximum CPU frequency - governor\n"
259 " CPU-ის მინიმალური სიხშირე - CPU-ის მაქსიმალური სიხშირე - "
378 msgid " current CPU frequency is "
570 msgid "analyzing CPU %d:\n"
571 msgstr "%d-ე CPU -ის ანალიზი:\n"
636 " except the -c CPU, --cpu CPU parameter\n"
643 " -c CPU, --cpu CPU -ის გარდა\n"
700 msgstr "CPU-ის დაყენება: %d\n"
840 msgid "Analyzing CPU %d:\n"
841 msgstr "%d-ე CPU -ის ანალიზი:\n"
[all …]
|
| A D | it.po | 235 " minimum CPU frequency - maximum CPU frequency - governor\n"
237 " frequenza minima CPU - frequenza massima CPU - gestore\n"
407 "la CPU *\n"
539 msgid "analyzing CPU %d:\n"
606 " except the -c CPU, --cpu CPU parameter\n"
615 " ad eccezione dell'opzione -c CPU o --cpu CPU\n"
796 msgid "Analyzing CPU %d:\n"
944 #~ " -c CPU, --cpu CPU CPU number which information shall be determined "
947 #~ " -c CPU, --cpu CPU Numero di CPU per la quale ottenere le "
951 #~ " -c CPU, --cpu CPU number of CPU where cpufreq settings shall be "
[all …]
|
| A D | fr.po | 235 " minimum CPU frequency - maximum CPU frequency - governor\n"
237 " Fréquence CPU minimale - Fréquence CPU maximale - régulateur\n"
536 msgid "analyzing CPU %d:\n"
537 msgstr "analyse du CPU %d :\n"
599 " except the -c CPU, --cpu CPU parameter\n"
787 msgid "Analyzing CPU %d:\n"
788 msgstr "analyse du CPU %d :\n"
936 #~ " -c CPU, --cpu CPU CPU number which information shall be determined "
939 #~ " -c CPU, --cpu CPU Numéro du CPU pour lequel l'information sera "
943 #~ " -c CPU, --cpu CPU number of CPU where cpufreq settings shall be "
[all …]
|
| A D | cs.po | 240 " minimum CPU frequency - maximum CPU frequency - governor\n"
242 " minimální frekvence CPU - maximální frekvence CPU - regulátor\n"
536 msgid "analyzing CPU %d:\n"
537 msgstr "analyzuji CPU %d:\n"
601 " except the -c CPU, --cpu CPU parameter\n"
787 msgid "Analyzing CPU %d:\n"
788 msgstr "analyzuji CPU %d:\n"
934 #~ " -c CPU, --cpu CPU CPU number which information shall be determined "
937 #~ " -c CPU, --cpu CPU Číslo CPU, o kterém se mají zjistit informace\n"
940 #~ " -c CPU, --cpu CPU number of CPU where cpufreq settings shall be "
[all …]
|
| A D | pt.po | 233 " minimum CPU frequency - maximum CPU frequency - governor\n"
235 " frequência mínina do CPU - frequência máxima do CPU - "
459 "do CPU *\n"
542 msgid "analyzing CPU %d:\n"
608 " except the -c CPU, --cpu CPU parameter\n"
617 " exceto com o parâmetro -c CPU, --cpu CPU\n"
798 msgid "Analyzing CPU %d:\n"
946 #~ " -c CPU, --cpu CPU CPU number which information shall be determined "
949 #~ " -c CPU, --cpu CPU número do CPU sobre o qual as inforções devem ser "
953 #~ " -c CPU, --cpu CPU number of CPU where cpufreq settings shall be "
[all …]
|
| A D | de.po | 249 " minimum CPU frequency - maximum CPU frequency - governor\n"
250 msgstr " minimale CPU-Frequenz - maximale CPU-Frequenz - Regler\n"
554 msgid "analyzing CPU %d:\n"
620 " except the -c CPU, --cpu CPU parameter\n"
686 msgstr "CPU einstellen: %d\n"
817 msgid "Analyzing CPU %d:\n"
822 msgid "CPU %u: No idle states\n"
965 #~ " -c CPU, --cpu CPU CPU number which information shall be determined "
968 #~ " -c CPU, --cpu CPU Nummer der CPU, über die Informationen "
972 #~ " -c CPU, --cpu CPU number of CPU where cpufreq settings shall be "
[all …]
|
| /tools/perf/Documentation/ |
| A D | cpu-and-latency-overheads.txt | 1 CPU and latency overheads
3 There are two notions of time: wall-clock time and CPU time.
7 Each second of wall-clock time we have number-of-cores seconds of CPU time.
9 'latency' columns for CPU and wall-clock time correspondingly).
11 Optimizing CPU overhead is useful to improve 'throughput', while optimizing
15 CPU utilization, while the latter may be useful to improve user-perceived
20 128 seconds of CPU time). The CPU overhead is: 'foo' - 6.6%, 'bar' - 93.4%.
22 running time of the program looking at the (wrong in this case) CPU overhead,
26 By default, perf shows only CPU overhead. To show latency overhead, use
55 CPU and wall-clock overheads:
|
| A D | perf-intel-pt.txt | 144 Dump all instructions in time range on CPU 1.
295 sample_type IP|TID|TIME|CPU|IDENTIFIER
446 MTC and TSC packets. A CYC packet contains the number of CPU
473 number of CPU cycles is:
479 packet is sent, not at, e.g. every 8 CPU cycles.
523 changes to the CPU C-state.
1570 CPU 0/KVM 0 [000] 0.000000: PERF_RECORD_COMM: CPU 0/KVM:13376/13381
1571 CPU 1/KVM 0 [000] 0.000000: PERF_RECORD_COMM: CPU 1/KVM:13376/13382
1572 CPU 2/KVM 0 [000] 0.000000: PERF_RECORD_COMM: CPU 2/KVM:13376/13383
1573 CPU 3/KVM 0 [000] 0.000000: PERF_RECORD_COMM: CPU 3/KVM:13376/13384
[all …]
|
| A D | perf-sched.txt | 36 It shows Runtime(time that a task spent actually running on the CPU),
49 threads can then replay the timings (CPU runtime and sleep patterns)
56 are running on a CPU. A '*' denotes the CPU that had the event, and
57 a dot signals an idle CPU.
105 --CPU <n>::
106 CPU to profile on.
161 Only show events for the given CPU(s) (comma separated list).
186 Show visual aid for sched switches by CPU: 'i' marks idle time,
|
| /tools/memory-model/Documentation/ |
| A D | glossary.txt | 30 load before later memory references running on that same CPU.
44 there is said to be a coherence link from the second CPU to
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
106 too late to affect the value returned by another CPU's
118 its CPU's prior accesses with all of that CPU's subsequent
120 that orders all of its CPU's prior accesses, itself, and
121 all of its CPU's subsequent accesses.
144 CPU, there is said to be a reads-from link from the second
[all …]
|
| A D | recipes.txt | 15 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
73 CPU during the time that CPU was holding this same lock". For example,
535 1. Write-to-read, where the next CPU reads the value that the
536 previous CPU wrote. The LB litmus-test patterns contain only
540 2. Read-to-write, where the next CPU overwrites the value that the
541 previous CPU read. The SB litmus test contains only this type
546 by the previous CPU. The Z6.0 litmus test pattern contains a
[all …]
|
| /tools/perf/pmu-events/ |
| A D | README | 14 - 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
126 to identify CPU (and associate it with a set of PMU events
137 is the pathname to the directory containing the CPU's JSON
[all …]
|
| /tools/testing/selftests/cgroup/ |
| A D | test_cpuset_prs.sh | 488 CPU=${1%=*}
490 CPUFILE=//sys/devices/system/cpu/cpu${CPU}/online
493 OFFLINE_CPUS="$OFFLINE_CPUS $CPU"
496 OFFLINE_CPUS=$(echo $CPU $CPU $OFFLINE_CPUS | fmt -1 |\
803 for ((CPU=0; CPU < $NR_CPUS; CPU++))
809 ISOLCPUS=$CPU
810 LASTISOLCPU=$CPU
811 elif [[ "$LASTISOLCPU" -eq $((CPU - 1)) ]]
818 LASTISOLCPU=$CPU
824 ISOLCPUS=${ISOLCPUS},$CPU
[all …]
|
| /tools/testing/selftests/sgx/ |
| A D | test_encl_bootstrap.S | 13 .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/arch/x86/kcpuid/ |
| A D | cpuid.csv | 13 # Maximum standard leaf number + CPU vendor string
186 # Extended CPU features enumeration
635 # Extended CPU feature identifiers
702 # CPU brand ID string, bytes 0 - 15
710 # CPU brand ID string, bytes 16 - 31
718 # CPU brand ID string, bytes 32 - 47
946 # AMD CPU topology enumeration
1078 # Transmeta extended CPU information
1104 # Transmeta CPU information string, bytes 0 - 15
1136 # Transmeta live CPU information
[all …]
|
| /tools/memory-model/litmus-tests/ |
| A D | MP+unlocklockonceonce+fencermbonceonce.litmus | 6 * 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
|
| A D | LB+unlocklockonceonce+poacquireonce.litmus | 6 * 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/ |
| A D | kvm-test-1-run-batch.sh | 65 print "echo No CPU-affinity information, so no taskset command.";
71 print "echo " scenario ": Bogus CPU-affinity information, so no taskset command.";
|
| /tools/power/cpupower/bench/ |
| A D | README-BENCH | 9 - 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/tests/ |
| A D | hists_output.c | 134 #define CPU(he) (he->cpu) macro
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()
567 CPU(he) == 1 && PID(he) == 100 && in test5()
574 CPU(he) == 1 && PID(he) == 100 && in test5()
[all …]
|
| /tools/perf/ |
| A D | design.txt | 10 thus be used to profile the code that runs on that CPU.
13 hardware capabilities. It provides per task and per CPU counters, counter
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
217 is on the CPU, it should be the only group using the CPU's counters.
226 CPU is in user, kernel and/or hypervisor mode.
251 The 'cpu' parameter allows a counter to be made specific to a CPU:
253 cpu >= 0: the counter is restricted to a specific CPU
259 events of that task and 'follows' that task to whatever CPU the task
264 all events on CPU-x. Per CPU counters need CAP_PERFMON or CAP_SYS_ADMIN
[all …]
|
| /tools/testing/selftests/rcutorture/configs/lock/ |
| A D | ver_functions.sh | 16 echo CPU-hotplug kernel, adding locktorture onoff. 1>&2
|
| /tools/testing/selftests/rcutorture/configs/scf/ |
| A D | ver_functions.sh | 16 echo CPU-hotplug kernel, adding scftorture onoff. 1>&2
|