| /linux/arch/powerpc/kernel/ |
| A D | hw_breakpoint.c | 126 struct breakpoint { struct
132 static DEFINE_PER_CPU(struct breakpoint *, cpu_bps[HBP_NUM_MAX]); argument
137 struct breakpoint *tmp; in alloc_breakpoint()
171 struct breakpoint *tmp; in task_bps_add()
186 struct breakpoint *tmp = list_entry(pos, struct breakpoint, list); in task_bps_remove()
202 struct breakpoint *tmp; in all_task_bps_check()
217 struct breakpoint *tmp; in same_task_bps_check()
229 struct breakpoint **cpu_bp; in cpu_bps_add()
230 struct breakpoint *tmp; in cpu_bps_add()
249 struct breakpoint **cpu_bp; in cpu_bps_remove()
[all …]
|
| /linux/Documentation/powerpc/ |
| A 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..
|
| A D | dawr-power9.rst | 80 PTRACE_GETHWDBGINFO) and setting the breakpoint, userspace will get an
|
| /linux/scripts/gdb/linux/ |
| A D | symbols.py | 68 breakpoint = None variable in LxSymbols
179 if self.breakpoint is not None:
180 self.breakpoint.delete()
181 self.breakpoint = None
182 self.breakpoint = LoadModuleBreakpoint(
|
| /linux/arch/sh/include/asm/ |
| A D | traps.h | 12 BUILD_TRAP_HANDLER(breakpoint);
|
| /linux/Documentation/trace/ |
| A 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
177 instruction instead of a breakpoint instruction at each probepoint.
183 Kprobes inserts an ordinary, breakpoint-based kprobe at the specified
216 - code to push the CPU's registers (emulating a breakpoint trap)
265 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 …]
|
| A D | ftrace-uses.rst | 107 to the pt_regs structure like it would be if an breakpoint was placed
|
| A D | ftrace.rst | 2730 a breakpoint at the location to be modified, sync all CPUs, modify
2731 the rest of the instruction not covered by the breakpoint. Sync
2732 all CPUs again, and then remove the breakpoint with the finished
|
| /linux/Documentation/dev-tools/ |
| A 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::
|
| A 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/kernel/debug/kdb/ |
| A D | kdb_cmds | 5 # be safe. Global breakpoint commands affect each cpu as it is booted.
|
| /linux/Documentation/virt/kvm/ |
| A 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/lib/ |
| A 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/arch/sh/kernel/ |
| A D | hw_breakpoint.c | 358 BUILD_TRAP_HANDLER(breakpoint) in BUILD_TRAP_HANDLER() argument
|
| /linux/samples/ |
| A D | Kconfig | 71 tristate "Build kernel hardware breakpoint examples -- loadable module only"
74 This builds kernel hardware breakpoint example modules.
|
| /linux/Documentation/input/devices/ |
| A 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/Documentation/networking/ |
| A D | tproxy.rst | 80 https://git.breakpoint.cc/cgit/fw/tcprdr.git/
|
| A D | filter.rst | 449 * breakpoint 0::
451 breakpoint at: l0: ldh [12]
453 * breakpoint 1::
455 breakpoint at: l1: jeq #0x800, l2, l5
461 break when a breakpoint is being hit (another `run` will continue from
462 the currently active breakpoint executing next instructions):
478 (breakpoint)
481 * breakpoint::
|
| /linux/drivers/scsi/hisi_sas/ |
| A D | hisi_sas.h | 451 struct hisi_sas_breakpoint *breakpoint; member
|
| A D | hisi_sas_main.c | 2400 memset(hisi_hba->breakpoint, 0, s); in hisi_sas_init_mem()
2513 hisi_hba->breakpoint = dmam_alloc_coherent(dev, s, in hisi_sas_alloc()
2516 if (!hisi_hba->breakpoint) in hisi_sas_alloc()
|
| /linux/arch/arm/kernel/ |
| A D | traps.c | 599 case NR(breakpoint): /* SWI BREAK_POINT */ in arm_syscall()
|
| /linux/arch/xtensa/ |
| A D | Kconfig | 492 it was possible to place a software breakpoint at 'reset' and
504 was mapped gdb wouldn't remove the breakpoint on hitting it as the
|
| /linux/Documentation/ia64/ |
| A D | fsys.rst | 216 breakpoint that triggers at any privilege level other than
|
| /linux/tools/perf/Documentation/ |
| A D | perf-record.txt | 90 - a hardware breakpoint event in the form of '\mem:addr[/len][:access]'
94 number of bytes from specified addr, which the breakpoint will cover.
|
| /linux/Documentation/livepatch/ |
| A D | livepatch.rst | 31 putting a breakpoint instruction instead of any instruction.
|