| /Linux-v5.4/Documentation/powerpc/ |
| D | ptrace.rst | 52 Sets a hardware breakpoint or watchpoint, according to the provided structure::
89 ptrace will return an integer (handle) uniquely identifying the breakpoint or
91 request to ask for its removal. Return -ENOSPC if the requested breakpoint
96 - set a breakpoint in the first breakpoint register::
126 - set a ranged hardware breakpoint::
154 Takes an integer which identifies an existing breakpoint or watchpoint
156 corresponding breakpoint or watchpoint..
|
| D | dawr-power9.rst | 80 PTRACE_GETHWDBGINFO) and setting the breakpoint, userspace will get an
|
| /Linux-v5.4/scripts/gdb/linux/ |
| D | symbols.py | 68 breakpoint = None variable in LxSymbols
177 if self.breakpoint is not None:
178 self.breakpoint.delete()
179 self.breakpoint = None
180 self.breakpoint = LoadModuleBreakpoint(
|
| /Linux-v5.4/arch/sh/include/asm/ |
| D | traps.h | 16 BUILD_TRAP_HANDLER(breakpoint);
|
| /Linux-v5.4/Documentation/virt/kvm/ |
| D | s390-diag.txt | 77 DIAGNOSE function code 'X'501 - KVM breakpoint
80 If the function code specifies 0x501, breakpoint functions may be performed.
|
| /Linux-v5.4/Documentation/dev-tools/ |
| D | gdb-kernel-debugging.rst | 83 - Set a breakpoint on some not yet loaded module function, e.g.::
87 Make breakpoint pending on future shared library load? (y or [n]) y
95 the breakpoint hit::
|
| D | kgdb.rst | 559 putting a breakpoint at ``sys_sync`` and then you can run ``sync`` from a
621 breakpoint operations, because it can disrupt the state of the kernel
698 implement HW breakpoint as well as the initialization to dynamically
751 - SW / HW breakpoint management for the kdb shell
|
| /Linux-v5.4/kernel/debug/kdb/ |
| D | kdb_cmds | 5 # be safe. Global breakpoint commands affect each cpu as it is booted.
|
| /Linux-v5.4/Documentation/ |
| D | kprobes.txt | 30 routine to be invoked when the breakpoint is hit.
65 with a breakpoint instruction (e.g., int3 on i386 and x86_64).
67 When a CPU hits the breakpoint instruction, a trap occurs, the CPU's
75 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
364 Sets a breakpoint at the address kp->addr. When the breakpoint is
403 Called with p pointing to the kprobe associated with the breakpoint,
[all …]
|
| /Linux-v5.4/lib/ |
| D | Kconfig.kgdb | 67 This will add an extra call back to kgdb for the breakpoint
93 0x0040 - allow flow control management (breakpoint, single step)
|
| /Linux-v5.4/samples/ |
| D | Kconfig | 43 tristate "Build kernel hardware breakpoint examples -- loadable module only"
46 This builds kernel hardware breakpoint example modules.
|
| /Linux-v5.4/arch/sh/kernel/ |
| D | hw_breakpoint.c | 358 BUILD_TRAP_HANDLER(breakpoint) in BUILD_TRAP_HANDLER() argument
|
| D | ptrace_64.c | 557 BUILD_TRAP_HANDLER(breakpoint) in BUILD_TRAP_HANDLER() argument
|
| /Linux-v5.4/Documentation/networking/ |
| D | tproxy.txt | 77 https://git.breakpoint.cc/cgit/fw/tcprdr.git/
|
| D | filter.txt | 418 > breakpoint 0
419 breakpoint at: l0: ldh [12]
420 > breakpoint 1
421 breakpoint at: l1: jeq #0x800, l2, l5
425 break when a breakpoint is being hit (another `run` will continue from
426 the currently active breakpoint executing next instructions):
441 (breakpoint)
444 > breakpoint
|
| /Linux-v5.4/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-v5.4/drivers/scsi/hisi_sas/ |
| D | hisi_sas.h | 378 struct hisi_sas_breakpoint *breakpoint; member
|
| D | hisi_sas_main.c | 2289 memset(hisi_hba->breakpoint, 0, s); in hisi_sas_init_mem()
2402 hisi_hba->breakpoint = dmam_alloc_coherent(dev, s, in hisi_sas_alloc()
2405 if (!hisi_hba->breakpoint) in hisi_sas_alloc()
|
| /Linux-v5.4/arch/arm/kernel/ |
| D | traps.c | 604 case NR(breakpoint): /* SWI BREAK_POINT */ in arm_syscall()
|
| /Linux-v5.4/arch/xtensa/ |
| D | Kconfig | 223 it was possible to place a software breakpoint at 'reset' and
235 was mapped gdb wouldn't remove the breakpoint on hitting it as the
|
| /Linux-v5.4/Documentation/trace/ |
| D | ftrace-uses.rst | 107 to the pt_regs structure like it would be if an breakpoint was placed
|
| /Linux-v5.4/tools/perf/Documentation/ |
| D | perf-record.txt | 83 - a hardware breakpoint event in the form of '\mem:addr[/len][:access]'
87 number of bytes from specified addr, which the breakpoint will cover.
|
| /Linux-v5.4/Documentation/ia64/ |
| D | fsys.rst | 216 breakpoint that triggers at any privilege level other than
|
| /Linux-v5.4/Documentation/livepatch/ |
| D | livepatch.rst | 44 putting a breakpoint instruction instead of any instruction.
|
| /Linux-v5.4/kernel/trace/ |
| D | Kconfig | 488 If kprobes can use ftrace instead of breakpoint, ftrace related
|
