| /linux-6.12.1/Documentation/arch/powerpc/ |
| D | ptrace.rst | 53 Sets a hardware breakpoint or watchpoint, according to the provided structure::
90 ptrace will return an integer (handle) uniquely identifying the breakpoint or
92 request to ask for its removal. Return -ENOSPC if the requested breakpoint
97 - set a breakpoint in the first breakpoint register::
127 - set a ranged hardware breakpoint::
155 Takes an integer which identifies an existing breakpoint or watchpoint
157 corresponding breakpoint or watchpoint..
|
| D | dawr-power9.rst | 88 PTRACE_GETHWDBGINFO) and setting the breakpoint, userspace will get an
|
| /linux-6.12.1/scripts/gdb/linux/ |
| D | symbols.py | 68 breakpoint = None variable in LxSymbols
182 if self.breakpoint is not None:
183 self.breakpoint.delete()
184 self.breakpoint = None
185 self.breakpoint = LoadModuleBreakpoint(
|
| /linux-6.12.1/arch/sh/include/asm/ |
| D | traps.h | 12 BUILD_TRAP_HANDLER(breakpoint);
|
| /linux-6.12.1/Documentation/trace/ |
| D | kprobes.rst | 31 routine to be invoked when the breakpoint is hit.
66 with a breakpoint instruction (e.g., int3 on i386 and x86_64).
68 When a CPU hits the breakpoint instruction, a trap occurs, the CPU's
76 but then Kprobes would have to temporarily remove the breakpoint
176 instruction instead of a breakpoint instruction at each probepoint.
182 Kprobes inserts an ordinary, breakpoint-based kprobe at the specified
215 - code to push the CPU's registers (emulating a breakpoint trap)
264 replaced with the original code (except for an int3 breakpoint in
365 Sets a breakpoint at the address kp->addr. When the breakpoint is hit, Kprobes
401 Called with p pointing to the kprobe associated with the breakpoint,
[all …]
|
| D | ftrace-uses.rst | 107 to the pt_regs structure like it would be if an breakpoint was placed
|
| /linux-6.12.1/tools/perf/bench/ |
| D | breakpoint.c | 42 struct breakpoint { struct
116 struct breakpoint *breakpoints; in bench_breakpoint_thread()
|
| D | Build | 18 perf-bench-y += breakpoint.o
|
| /linux-6.12.1/kernel/debug/kdb/ |
| D | kdb_cmds | 5 # be safe. Global breakpoint commands affect each cpu as it is booted.
|
| /linux-6.12.1/Documentation/dev-tools/ |
| D | gdb-kernel-debugging.rst | 87 - Set a breakpoint on some not yet loaded module function, e.g.::
91 Make breakpoint pending on future shared library load? (y or [n]) y
99 the breakpoint hit::
|
| D | kgdb.rst | 582 putting a breakpoint at ``sys_sync`` and then you can run ``sync`` from a
644 breakpoint operations, because it can disrupt the state of the kernel
721 implement HW breakpoint as well as the initialization to dynamically
774 - SW / HW breakpoint management for the kdb shell
|
| /linux-6.12.1/Documentation/virt/kvm/s390/ |
| D | s390-diag.rst | 80 DIAGNOSE function code 'X'501 - KVM breakpoint
83 If the function code specifies 0x501, breakpoint functions may be performed.
|
| /linux-6.12.1/Documentation/networking/ |
| D | filter.rst | 456 * breakpoint 0::
458 breakpoint at: l0: ldh [12]
460 * breakpoint 1::
462 breakpoint at: l1: jeq #0x800, l2, l5
468 break when a breakpoint is being hit (another `run` will continue from
469 the currently active breakpoint executing next instructions):
485 (breakpoint)
488 * breakpoint::
|
| D | tproxy.rst | 80 https://git.breakpoint.cc/cgit/fw/tcprdr.git/
|
| /linux-6.12.1/Documentation/core-api/ |
| D | entry.rst | 24 which means that (for example) a breakpoint in the breakpoint entry code would
25 overwrite the debug registers of the initial breakpoint.
|
| /linux-6.12.1/lib/ |
| D | Kconfig.kgdb | 87 This will add an extra call back to kgdb for the breakpoint
113 0x0040 - allow flow control management (breakpoint, single step)
|
| /linux-6.12.1/arch/sh/kernel/ |
| D | hw_breakpoint.c | 358 BUILD_TRAP_HANDLER(breakpoint) in BUILD_TRAP_HANDLER() argument
|
| /linux-6.12.1/Documentation/translations/zh_CN/dev-tools/ |
| D | gdb-kernel-debugging.rst | 85 Make breakpoint pending on future shared library load? (y or [n]) y
|
| /linux-6.12.1/Documentation/translations/zh_TW/dev-tools/ |
| D | gdb-kernel-debugging.rst | 81 Make breakpoint pending on future shared library load? (y or [n]) y
|
| /linux-6.12.1/samples/ |
| D | Kconfig | 84 tristate "Build kernel hardware breakpoint examples -- loadable module only"
87 This builds kernel hardware breakpoint example modules.
|
| /linux-6.12.1/Documentation/input/devices/ |
| D | atarikbd.rst | 170 equivalent cursor control keystroke(s). The ikbd provides a single breakpoint
525 ; horizontal velocity breakpoint is reached
527 ; vertical velocity breakpoint is reached
544 seconds. After the Rn breakpoint is reached, keystroke pairs are generated
545 every Vn tenths of seconds. This provides a velocity (auto-repeat) breakpoint
|
| /linux-6.12.1/drivers/scsi/hisi_sas/ |
| D | hisi_sas.h | 445 struct hisi_sas_breakpoint *breakpoint; member
|
| D | hisi_sas_main.c | 2164 memset(hisi_hba->breakpoint, 0, s); in hisi_sas_init_mem()
2278 hisi_hba->breakpoint = dmam_alloc_coherent(dev, s, in hisi_sas_alloc()
2281 if (!hisi_hba->breakpoint) in hisi_sas_alloc()
|
| /linux-6.12.1/arch/arm/kernel/ |
| D | traps.c | 623 case NR(breakpoint): /* SWI BREAK_POINT */ in arm_syscall()
|
| /linux-6.12.1/arch/xtensa/ |
| D | Kconfig | 575 it was possible to place a software breakpoint at 'reset' and
587 was mapped gdb wouldn't remove the breakpoint on hitting it as the
|