Home
last modified time | relevance | path

Searched refs:interrupt (Results 1 – 16 of 16) sorted by relevance

/tools/testing/selftests/arm64/fp/
Dsve-stress30 interrupt () { function
40 trap interrupt INT TERM EXIT
Dfpsimd-stress30 interrupt () { function
40 trap interrupt INT TERM EXIT
/tools/lib/traceevent/Documentation/
Dlibtraceevent-event_print.txt32 fields - interrupt state, scheduling state,
34 Field 1 is the interrupt enabled state:
46 s : Soft interrupt context
47 h : Hard interrupt context
48 H : Hard interrupt context which triggered
49 during soft interrupt context.
52 interrupt context
/tools/hv/
Dvmbus_testing227 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/
Dhmi.sh28 dmesg | grep -c 'Harmless Hypervisor Maintenance interrupt'
/tools/perf/Documentation/
Dperf-intel-pt.txt112 system, asynchronous, interrupt, transaction abort, trace begin, trace end,
113 in transaction, VM-entry, VM-exit, interrupt disabled, and interrupt disable
163 (e.g. page fault or interrupt), then the instruction count does not include the
668 buffers are logically concatenated. However an interrupt must be used to switch
670 a) the interrupt may not be handled in time so that the current buffer
1113 One example of that would be when the buffer-switching interrupt has been too
1378 1 INTR interrupt, fault, exception, NMI
1379 2 IRET interrupt return
1380 3 SMI system management interrupt
1382 5 SIPI startup interprocessor interrupt
[all …]
Dperf-ftrace.txt112 noirqs - Ignore functions that happen inside interrupt.
Dperf-script.txt199 call, return, conditional, system, asynchronous, interrupt,
Dperf-record.txt426 Capture machine state (registers) at interrupt, i.e., on counter overflows for
/tools/arch/x86/include/uapi/asm/
Dkvm.h347 } interrupt; member
/tools/perf/
Ddesign.txt174 A "sampling" counter is one that is set up to generate an interrupt
177 interrupt:
/tools/memory-model/Documentation/
Daccess-marking.txt199 c. When one of the stores is in an interrupt handler and
308 If you need KCSAN to detect such a write happening in an interrupt handler
Dordering.txt235 in the case where an interrupt handler terminates the loop. Another way
Dlitmus-tests.txt970 this limitation can be overcome by modeling the interrupt or
Dexplanation.txt101 driver might contain an interrupt handler which collects data from the
131 Here the P0() function represents the interrupt handler running on one
/tools/objtool/Documentation/
Dstack-validation.txt92 [*] unless an interrupt or exception has occurred at the very