Searched refs:breakpoints (Results 1 – 20 of 20) sorted by relevance
| /Linux-v6.6/tools/perf/bench/ |
| D | breakpoint.c | 116 struct breakpoint *breakpoints; in bench_breakpoint_thread() local
124 breakpoints = calloc(thread_params.nbreakpoints, sizeof(breakpoints[0])); in bench_breakpoint_thread()
126 if (!breakpoints || !parallel) in bench_breakpoint_thread()
130 breakpoints[i].fd = breakpoint_setup(&breakpoints[i].watched); in bench_breakpoint_thread()
132 if (breakpoints[i].fd < 0) { in bench_breakpoint_thread()
133 if (breakpoints[i].fd == -ENODEV) { in bench_breakpoint_thread()
150 close(breakpoints[i].fd); in bench_breakpoint_thread()
152 free(breakpoints); in bench_breakpoint_thread()
|
| /Linux-v6.6/Documentation/powerpc/ |
| D | ptrace.rst | 8 4 hardware breakpoints (IAC)
28 GDB: this query will return the number of hardware breakpoints, hardware
86 With this GDB can ask for all kinds of hardware breakpoints and watchpoints
87 that the BookE supports. COMEFROM breakpoints available in server processors
|
| D | dawr-power9.rst | 33 For ptrace, we now advertise zero breakpoints on POWER9 via the
87 enabled/disabled between getting the number of breakpoints (via
|
| /Linux-v6.6/scripts/gdb/linux/ |
| D | symbols.py | 147 if hasattr(gdb, 'breakpoints') and not gdb.breakpoints() is None:
148 for bp in gdb.breakpoints():
|
| /Linux-v6.6/lib/ |
| D | Kconfig.kgdb | 28 bool "KGDB: use kprobe blocklist to prohibit unsafe breakpoints"
35 identify symbols where it is unsafe to set breakpoints.
158 still try to register kgdb to handle breakpoints and crashes
|
| /Linux-v6.6/Documentation/dev-tools/ |
| D | kgdb.rst | 17 memory, registers, process lists, dmesg, and even set breakpoints to
19 you can set breakpoints and execute some basic kernel run control. Kdb
30 application. It is possible to place breakpoints in kernel code and
72 option will prevent the use of software breakpoints because it marks
75 breakpoints if you desire to run with the ``CONFIG_STRICT_KERNEL_RWX``
645 debugger. You should be using gdb for breakpoints and run control
707 - A full implementation for software breakpoints unless overridden
737 - (optional) HW breakpoints
|
| D | kselftest.rst | 115 $ make TARGETS="bpf breakpoints size timers" SKIP_TARGETS=bpf kselftest
|
| D | kcsan.rst | 240 breakpoints).
|
| /Linux-v6.6/arch/arc/kernel/ |
| D | entry.S | 223 ;============ TRAP N : breakpoints, kprobes etc
|
| /Linux-v6.6/tools/testing/selftests/ |
| D | Makefile | 6 TARGETS += breakpoints
|
| /Linux-v6.6/Documentation/networking/ |
| D | filter.rst | 466 Sets breakpoints at particular BPF instructions. Issuing a `run` command
490 breakpoints: 0 1
492 Prints currently set breakpoints.
|
| /Linux-v6.6/tools/arch/x86/kcpuid/ |
| D | cpuid.csv | 378 …icates support for address mask extension (to 32 bits and to all 4 DRs) for instruction breakpoints
382 0x80000001, 0, EDX, 2, de, Debugging extensions, IO breakpoints, CR4.DE
|
| /Linux-v6.6/Documentation/core-api/ |
| D | entry.rst | 205 whether these exceptions happened in user-space (breakpoints or watchpoints) or
|
| /Linux-v6.6/arch/ |
| D | Kconfig | 128 ( These probes come in the form of single-byte breakpoints,
395 Depending on the arch implementation of hardware breakpoints,
397 breakpoints addresses, others have mixed registers to store
399 Select this option if your arch implements breakpoints under the
|
| /Linux-v6.6/arch/xtensa/ |
| D | Kconfig | 573 then enter your normal kernel breakpoints once the MMU was mapped
581 use hardware breakpoints (gdb 'hbreak' cmd) to break at _startup.
|
| /Linux-v6.6/Documentation/security/ |
| D | self-protection.rst | 54 alternatives, breakpoints, kprobes, etc. If these must exist in a
|
| /Linux-v6.6/tools/include/uapi/linux/ |
| D | kvm.h | 80 struct kvm_breakpoint breakpoints[4]; member
|
| /Linux-v6.6/include/uapi/linux/ |
| D | kvm.h | 80 struct kvm_breakpoint breakpoints[4]; member
|
| /Linux-v6.6/drivers/scsi/aic7xxx/ |
| D | aic79xx.reg | 3396 * single step, breakpoints and program load.
|
| /Linux-v6.6/Documentation/virt/kvm/ |
| D | api.rst | 3624 - KVM_GUESTDBG_USE_SW_BP: using software breakpoints [x86, arm64]
3625 - KVM_GUESTDBG_USE_HW_BP: using hardware breakpoints [x86, s390]
3632 For example KVM_GUESTDBG_USE_SW_BP indicates that software breakpoints
7186 mechanism e.g. to realize 2-byte software breakpoints. The kernel will
|
