Searched refs:interrupt (Results 1 – 20 of 20) sorted by relevance
| /tools/testing/selftests/arm64/fp/ |
| A D | sve-stress | 30 interrupt () {
40 trap interrupt INT TERM EXIT
|
| A D | ssve-stress | 30 interrupt () {
40 trap interrupt INT TERM EXIT
|
| A D | za-stress | 30 interrupt () {
40 trap interrupt INT TERM EXIT
|
| A D | fpsimd-stress | 30 interrupt () {
40 trap interrupt INT TERM EXIT
|
| /tools/hv/ |
| A D | vmbus_testing | 227 interrupt = file_map[device][f_names.buff_f.value]
232 write_test_files(interrupt, delay_length[0])
237 .format(read_test_files(interrupt),
238 interrupt.split("/")[5]))
245 .format(errno, strerror, interrupt, message))
|
| /tools/testing/selftests/powerpc/scripts/ |
| A D | hmi.sh | 28 dmesg | grep -c 'Harmless Hypervisor Maintenance interrupt'
|
| /tools/perf/Documentation/ |
| A D | perf-arm-spe.txt | 17 events down to individual instructions. Rather than being interrupt-driven, it picks an
58 When the buffer fills, an interrupt is sent and the driver signals Perf to collect the records.
123 The SPE interrupt must also be described by the firmware. If the module is loaded and KPTI is
125 /sys/bus/event_source/devices/, then it's possible that the SPE interrupt isn't described by
212 Module not built or loaded, KPTI not disabled, interrupt not described by firmware,
|
| A D | itrace.txt | 11 I synthesize interrupt or similar (asynchronous) events
|
| A D | perf-ftrace.txt | 131 - noirqs - Ignore functions that happen inside interrupt.
218 - noirqs - Ignore functions that happen inside interrupt.
|
| A D | perf-intel-pt.txt | 112 system, asynchronous, interrupt, transaction abort, trace begin, trace end,
113 in transaction, VM-entry, VM-exit, interrupt disabled, and interrupt disable
179 (e.g. page fault or interrupt), then the instruction count does not include the
748 a) the interrupt may not be handled in time so that the current buffer
1743 1 INTR interrupt, fault, exception, NMI
1744 2 IRET interrupt return
1745 3 SMI system management interrupt
1747 5 SIPI startup interprocessor interrupt
1751 9 VMEXIT_INTR VM-Exit due to interrupt
1781 where "via branch" indicates a branch (interrupt or return from interrupt) and
[all …]
|
| A D | perf-script.txt | 204 call, return, conditional, system, asynchronous, interrupt,
206 VM-Exit, interrupt disabled and interrupt disable toggle respectively.
|
| A D | perf-record.txt | 507 Capture machine state (registers) at interrupt, i.e., on counter overflows for
|
| /tools/perf/ |
| A D | design.txt | 177 A "sampling" counter is one that is set up to generate an interrupt
180 interrupt:
|
| /tools/arch/x86/include/uapi/asm/ |
| A D | kvm.h | 348 } interrupt; member
|
| /tools/memory-model/Documentation/ |
| A D | access-marking.txt | 205 c. When one of the stores is in an interrupt handler and
331 If you need KCSAN to detect such a write happening in an interrupt handler
|
| A D | ordering.txt | 235 in the case where an interrupt handler terminates the loop. Another way
|
| A D | litmus-tests.txt | 987 this limitation can be overcome by modeling the interrupt or
|
| A D | explanation.txt | 102 driver might contain an interrupt handler which collects data from the
132 Here the P0() function represents the interrupt handler running on one
|
| /tools/objtool/Documentation/ |
| A D | objtool.txt | 184 [*] unless an interrupt or exception has occurred at the very
|
| /tools/arch/x86/kcpuid/ |
| A D | cpuid.csv | 843 0x8000000a, 0, edx, 13, avic , Advanced virtual interrupt contro…
|
Completed in 31 milliseconds