| /tools/perf/Documentation/ |
| D | itrace.txt | 1 i synthesize instructions events
27 for instructions events can be specified in units of:
29 i instructions
35 Also the call chain size (default 16, max. 1024) for instructions or
39 instructions or transactions events can be specified.
45 It is also possible to skip events generated (instructions, branches, transactions,
50 skips the first million instructions.
|
| D | tips.txt | 2 Sample related events with: perf record -e '{cycles,instructions}:S'
29 See assembly instructions with percentage: perf annotate <symbol>
42 To show IPC for sampling periods use perf record -e '{cycles,instructions}:S' and then browse conte…
|
| D | perf-intel-pt.txt | 34 samples output by perf hardware events, for example as though the "instructions"
119 Dump all instructions. This requires installing the xed tool (see XED below)
120 Dumping all instructions in a long trace can be fairly slow. It is usually better
139 Dump all instructions in time range on CPU 1.
146 There are two ways that instructions-per-cycle (IPC) can be calculated depending
156 of instructions and number of cycles since the last update, and thus represent
158 events is calculated separately from IPC for "instructions" events.
169 value, "instructions" events can be used e.g. --itrace=i0ns
857 i synthesize "instructions" events
874 instructions".
[all …]
|
| D | perf-list.txt | 180 like cycles and instructions and some software events.
236 perf stat -e '{instructions,cycles}' ...
241 for the core, plus three fixed counters for instructions, cycles and
261 perf record -e '{cycles,instructions}:S' ...
|
| D | intel-bts.txt | 54 "instructions" events nor "transactions" events (and consequently call
|
| D | perf-annotate.txt | 98 Show raw instruction encoding of assembly instructions.
|
| D | examples.txt | 190 and check which instructions/source-code generated page allocations:
|
| /tools/testing/selftests/powerpc/pmu/ |
| D | count_instructions.c | 29 static int do_count_loop(struct event *events, u64 instructions, in do_count_loop() argument
38 thirty_two_instruction_loop(instructions >> 5); in do_count_loop()
45 expected = instructions + overhead; in do_count_loop()
53 printf("Looped for %llu instructions, overhead %llu\n", instructions, overhead); in do_count_loop()
|
| D | count_stcx_fail.c | 29 static int do_count_loop(struct event *events, u64 instructions, in do_count_loop() argument
39 thirty_two_instruction_loop_with_ll_sc(instructions >> 5, &dummy); in do_count_loop()
47 expected = instructions + overhead + (events[2].result.value * 10); in do_count_loop()
57 printf("Looped for %llu instructions, overhead %llu\n", instructions, overhead); in do_count_loop()
|
| /tools/testing/selftests/powerpc/pmu/ebb/ |
| D | instruction_count_test.c | 25 static int do_count_loop(struct event *event, uint64_t instructions, in do_count_loop() argument
37 thirty_two_instruction_loop(instructions >> 5); in do_count_loop()
46 expected = instructions + overhead; in do_count_loop()
51 printf("Looped for %lu instructions, overhead %lu\n", instructions, overhead); in do_count_loop()
|
| /tools/memory-model/ |
| D | linux-kernel.bell | 20 instructions R[{'once,'acquire,'noreturn}]
21 instructions W[{'once,'release}]
22 instructions RMW[{'once,'acquire,'release}]
35 instructions F[Barriers]
39 instructions SRCU[SRCU]
|
| D | README | 28 See "herdtools7/INSTALL.md" for installation instructions.
186 Categorizes the relevant instructions, including memory
|
| /tools/perf/tests/attr/ |
| D | README | 50 perf record --group -e cycles,instructions kill (test-record-group)
51 perf record -e '{cycles,instructions}' kill (test-record-group1)
52 perf record -e '{cycles/period=1/,instructions/period=2/}:S' kill (test-record-group2)
64 perf stat --group -e cycles,instructions kill (test-stat-group)
65 perf stat -e '{cycles,instructions}' kill (test-stat-group1)
|
| D | test-stat-group1 | 3 args = -e '{cycles,instructions}' kill >/dev/null 2>&1
|
| D | test-stat-group | 3 args = --group -e cycles,instructions kill >/dev/null 2>&1
|
| D | test-record-group | 3 args = --no-bpf-event --group -e cycles,instructions kill >/dev/null 2>&1
|
| D | test-record-group1 | 3 args = --no-bpf-event -e '{cycles,instructions}' kill >/dev/null 2>&1
|
| D | test-record-group2 | 3 args = --no-bpf-event -e '{cycles/period=1234000/,instructions/period=6789000/}:S' kill >/dev/nu…
|
| /tools/testing/selftests/bpf/ |
| D | README.rst | 4 General instructions on running selftests can be found in
24 // the instructions below will not be seen in the verifier log
|
| /tools/objtool/Documentation/ |
| D | stack-validation.txt | 20 instructions). Similarly, it knows how to follow switch statements, for
44 For C code, gcc automatically generates instructions for setting up
47 But for asm code, the frame setup instructions have to be written by
73 replacing the frame pointer related instructions with nops, here's
159 5. A callable function may not execute kernel entry/exit instructions.
160 The only code which needs such instructions is kernel entry code,
236 instructions aren't allowed in a callable function, and are most
|
| /tools/bpf/bpftool/Documentation/ |
| D | bpftool-prog.rst | 54 | **cycles** | **instructions** | **l1d_loads** | **llc_misses**
84 Dump eBPF instructions of the programs from the kernel. By
97 built instead, and eBPF instructions will be presented with
321 | **# bpftool prog profile id 337 duration 10 cycles instructions llc_misses**
327 42518139 instructions # 1.06 insns per cycle (83.39%)
|
| /tools/memory-model/Documentation/ |
| D | explanation.txt | 73 load instructions. The LKMM makes these predictions for code running
184 if each CPU executed its instructions in order but with unspecified
185 timing. In other words, the instructions from the various CPUs get
187 global order that agrees with the order of the instructions in the
200 their instructions in order.
207 its instructions in order.
258 be; consider for example the order of instructions in a program's
260 important assumption that CPUs execute instructions in the same order
261 as those instructions occur in the code, and there are many other
312 logical computations, control-flow instructions, or accesses to
[all …]
|
| /tools/perf/util/ |
| D | parse-events.l | 331 instructions { return sym(yyscanner, PERF_TYPE_HARDWARE, PERF_COUNT_HW_INSTRUCTIONS); }
334 branch-instructions|branches { return sym(yyscanner, PERF_TYPE_HARDWARE, PERF_COUNT_HW_BRANCH_INS…
|
| D | annotate.c | 77 struct ins *instructions; member
108 if (arch->nr_instructions_allocated == 0 && arch->instructions) in arch__grow_instructions()
112 new_instructions = realloc(arch->instructions, new_nr_allocated * sizeof(struct ins)); in arch__grow_instructions()
117 arch->instructions = new_instructions; in arch__grow_instructions()
127 memcpy(new_instructions, arch->instructions, arch->nr_instructions); in arch__grow_instructions()
139 ins = &arch->instructions[arch->nr_instructions]; in arch__associate_ins_ops()
180 .instructions = x86__instructions,
686 qsort(arch->instructions, nmemb, sizeof(struct ins), ins__cmp); in ins__sort()
699 ins = bsearch(name, arch->instructions, nmemb, sizeof(struct ins), ins__key_cmp); in __ins__find()
|
| /tools/usb/usbip/ |
| D | INSTALL | 15 more-detailed instructions are generic; see the `README' file for
16 instructions specific to this package.
35 diffs or instructions to the address given in the `README' so they can
|