| /linux/tools/perf/tests/shell/ |
| A D | stat_bpf_counters.sh | 44 …base_instructions=$(perf stat --no-big-num -e instructions -- $workload 2>&1 | awk '/instructions/…
45 …bpf_instructions=$(perf stat --no-big-num --bpf-counters -e instructions -- $workload 2>&1 | awk …
54 …stat_output=$(perf stat --no-big-num -e instructions/name=base_instructions/,instructions/name=bpf…
63 if ! perf stat -e instructions --bpf-counters true > /dev/null 2>&1; then
66 perf --no-pager stat -e instructions --bpf-counters true || true
|
| A D | stat+shadow_stat.sh | 17 perf stat -a --no-big-num -e cycles,instructions sleep 1 2>&1 | \
18 grep -e cycles -e instructions | \
56 perf stat -a -A --no-big-num -e cycles,instructions sleep 1 2>&1 | \
|
| /linux/Documentation/arch/arm64/ |
| A D | legacy_instructions.rst | 2 Legacy instructions
6 emulation of instructions which have been deprecated, or obsoleted in
18 Generates undefined instruction abort. Default for instructions that
27 instructions, .e.g., CP15 barriers
34 instructions. Using hardware execution generally provides better
36 about the use of the deprecated instructions.
39 architecture. Deprecated instructions should default to emulation
40 while obsolete instructions must be undefined by default.
45 Supported legacy instructions
|
| A D | pointer-authentication.rst | 25 The extension adds instructions to insert a valid PAC into a pointer,
30 A subset of these instructions have been allocated from the HINT
32 these instructions behave as NOPs. Applications and libraries using
33 these instructions operate correctly regardless of the presence of the
57 with HINT space pointer authentication instructions protecting
107 register. Any attempt to use the Pointer Authentication instructions will
128 instructions to sign and authenticate function pointers and other pointers
135 but before executing any PAC instructions.
|
| /linux/Documentation/bpf/standardization/ |
| A D | instruction-set.rst | 146 and modulo instructions.
287 Arithmetic and jump instructions
315 Arithmetic instructions
374 Note that most arithmetic instructions have 'offset' set to 0. Only three instructions
427 Byte swap instructions
441 .. table:: Byte swap instructions
476 Jump instructions
485 .. table:: Jump instructions
570 Load and store instructions
588 IMM 0 64-bit immediate instructions `64-bit immediate instructions`_
[all …]
|
| /linux/drivers/watchdog/ |
| A D | wdat_wdt.c | 119 if (action >= ARRAY_SIZE(wdat->instructions)) in wdat_wdt_run_action()
122 if (!wdat->instructions[action]) in wdat_wdt_run_action()
376 struct list_head *instructions; in wdat_wdt_probe() local
423 instructions = wdat->instructions[action]; in wdat_wdt_probe()
424 if (!instructions) { in wdat_wdt_probe()
425 instructions = devm_kzalloc(dev, in wdat_wdt_probe()
426 sizeof(*instructions), in wdat_wdt_probe()
428 if (!instructions) in wdat_wdt_probe()
431 INIT_LIST_HEAD(instructions); in wdat_wdt_probe()
432 wdat->instructions[action] = instructions; in wdat_wdt_probe()
[all …]
|
| /linux/Documentation/bpf/ |
| A D | linux-notes.rst | 10 Byte swap instructions
15 Jump instructions
45 Legacy BPF Packet access instructions
49 <instruction-set.html#legacy-bpf-packet-access-instructions>`_,
50 Linux has special eBPF instructions for access to packet data that have been
54 The instructions come in two forms: ``BPF_ABS | <size> | BPF_LD`` and
57 These instructions are used to access packet data and can only be used when
63 These instructions have seven implicit operands:
72 These instructions have an implicit program exit condition as well. If an
|
| A D | bpf_design_QA.rst | 93 It's the maximum number of instructions that the unprivileged bpf
95 Like the maximum number of instructions that can be explored during
119 Q: LD_ABS and LD_IND instructions vs C code
129 Q: BPF instructions mapping not one-to-one to native CPU
131 Q: It seems not all BPF instructions are one-to-one to native CPU.
149 of LD_ABS insn). Those instructions need to invoke epilogue and
156 due to lack of these compare instructions and they were added.
157 These two instructions is a perfect example what kind of new BPF
158 instructions are acceptable and can be added in the future.
159 These two already had equivalent instructions in native CPUs.
[all …]
|
| A D | clang-notes.rst | 17 Arithmetic instructions
23 Jump instructions
32 Clang can generate atomic instructions by default when ``-mcpu=v3`` is
|
| /linux/Documentation/devicetree/bindings/riscv/ |
| A D | extensions.yaml | 386 instructions, as ratified in the 20191213 version of the
431 instructions, as ratified in commit 56ed795 ("Update
437 instructions, as ratified in commit 56ed795 ("Update
485 instructions, as ratified in commit 56ed795 ("Update
509 instructions, as ratified in commit 56ed795 ("Update
515 instructions, as ratified in commit 56ed795 ("Update
521 hash (SHA-256 only) instructions, as ratified in commit
533 instructions, as ratified in commit 56ed795 ("Update
545 instructions, as ratified in commit 56ed795 ("Update
551 instructions, as ratified in commit 56ed795 ("Update
[all …]
|
| /linux/tools/perf/Documentation/ |
| A D | itrace.txt | 1 i synthesize instructions events
34 for instructions events can be specified in units of:
36 i instructions
42 Also the call chain size (default 16, max. 1024) for instructions or
46 instructions or transactions events can be specified.
52 It is also possible to skip events generated (instructions, branches, transactions,
57 skips the first million instructions.
|
| A D | intel-hybrid.txt | 29 [Fixed Counter: Counts the number of instructions retired. Unit: cpu_atom]
31 [Number of instructions retired. Fixed Counter - architectural event. Unit: cpu_core]
184 cpu_core/instructions/,
185 cpu_atom/instructions/,
199 perf stat -e cpu_core/cycles/,cpu_atom/instructions/
200 perf stat -e '{cpu_core/cycles/,cpu_core/instructions/}'
202 But '{cpu_core/cycles/,cpu_atom/instructions/}' will return
|
| /linux/Documentation/arch/arm/ |
| A D | swp_emulation.rst | 4 ARMv6 architecture deprecates use of the SWP/SWPB instructions, and recommends
5 moving to the load-locked/store-conditional instructions LDREX and STREX.
8 instructions, triggering an undefined instruction exception when executed.
9 Trapped instructions are emulated using an LDREX/STREX or LDREXB/STREXB
|
| A D | kernel_mode_neon.rst | 7 * Use only NEON instructions, or VFP instructions that don't rely on support
19 It is possible to use NEON instructions (and in some cases, VFP instructions) in
24 may call schedule()], as NEON or VFP instructions will be executed in a
43 should be called before any kernel mode NEON or VFP instructions are issued.
74 Such software assistance is currently not implemented for VFP instructions
82 kernel_neon_end(), i.e., that it is only allowed to issue NEON/VFP instructions
84 instructions of its own at -O3 level if -mfpu=neon is selected, and even if the
86 instructions appearing in unexpected places if no special care is taken.
98 both NEON and VFP instructions will only ever appear in designated compilation
|
| /linux/Documentation/arch/x86/x86_64/ |
| A D | fsgs.rst | 69 Accessing FS/GS base with the FSGSBASE instructions
73 instructions to access the FS and GS base registers directly from user
74 space. These instructions are also supported on AMD Family 17H CPUs. The
75 following instructions are available:
90 FSGSBASE instructions enablement argument
92 The instructions are enumerated in CPUID leaf 7, bit 0 of EBX. If
95 The availability of the instructions does not enable them
103 instructions will fault with a #UD exception.
107 kernel has FSGSBASE instructions enabled and applications can use them.
125 FSGSBASE instructions compiler support argument
[all …]
|
| /linux/tools/testing/selftests/powerpc/pmu/ |
| A 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()
|
| A 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()
|
| /linux/tools/testing/selftests/powerpc/pmu/ebb/ |
| A 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()
|
| /linux/arch/sparc/crypto/ |
| A D | Kconfig | 37 Architecture: sparc64 using crypto instructions, when available
57 Architecture: sparc64 using crypto instructions, when available
67 Architecture: sparc64 using crypto instructions, when available
77 Architecture: sparc64 using crypto instructions
|
| /linux/tools/memory-model/ |
| A D | linux-kernel.bell | 20 instructions R[{'once,'acquire,'noreturn}]
21 instructions W[{'once,'release}]
22 instructions RMW[{'once,'acquire,'release}]
36 instructions F[Barriers]
40 instructions SRCU[SRCU]
|
| /linux/Documentation/virt/kvm/ |
| A D | ppc-pv.rst | 9 instructions and can emulate them accordingly.
12 instructions that needlessly return us to the hypervisor even though they
15 This is what the PPC PV interface helps with. It takes privileged instructions
35 'hypercall-instructions'. This property contains at most 4 opcodes that make
36 up the hypercall. To call a hypercall, just call these instructions.
138 Patched instructions
141 The "ld" and "std" instructions are transformed to "lwz" and "stw" instructions
147 also act on the shared page. So calling privileged instructions still works as
187 Some instructions require more logic to determine what's going on than a load
189 RAM around where we can live translate instructions to. What happens is the
|
| /linux/arch/mips/crypto/ |
| A D | Kconfig | 31 Architecture: mips OCTEON using crypto instructions, when available
51 Architecture: mips OCTEON using crypto instructions, when available
61 Architecture: mips OCTEON using crypto instructions, when available
|
| /linux/Documentation/virt/ |
| A D | paravirt_ops.rst | 16 corresponding to low-level critical instructions and high-level
28 Usually these operations correspond to low-level critical instructions. They
34 because they include sensitive instructions or some code paths in
|
| /linux/arch/powerpc/crypto/ |
| A D | Kconfig | 46 powerpc64 AltiVec extensions (POWER8 vpmsum instructions).
123 Support for cryptographic acceleration instructions on Power10 or
153 bool "Support for VMX cryptographic acceleration instructions"
156 Support for VMX cryptographic acceleration instructions.
168 Support for VMX cryptographic acceleration instructions on Power8 CPU.
|
| /linux/arch/arm/kernel/ |
| A D | phys2virt.S | 41 mov r0, r3, lsr #21 @ constant for add/sub instructions
77 @ In the non-LPAE case, all patchable instructions are MOVW
78 @ instructions, where we need to patch in the offset into the
131 @ in BE8, we load data in BE, but instructions still in LE
155 @ In the non-LPAE case, all patchable instructions are ADD or SUB
156 @ instructions, where we need to patch in the offset into the
173 @ instructions based on bits 23:22 of the opcode, and ADD/SUB can be
|