Home
last modified time | relevance | path

Searched refs:breakpoint (Results 1 – 25 of 29) sorted by relevance

12

/Linux-v5.15/arch/powerpc/kernel/
Dhw_breakpoint.c126 struct breakpoint { struct
132 static DEFINE_PER_CPU(struct breakpoint *, cpu_bps[HBP_NUM_MAX]); argument
135 static struct breakpoint *alloc_breakpoint(struct perf_event *bp) in alloc_breakpoint()
137 struct breakpoint *tmp; in alloc_breakpoint()
159 static bool alternate_infra_bp(struct breakpoint *b, struct perf_event *bp) in alternate_infra_bp()
164 static bool can_co_exist(struct breakpoint *b, struct perf_event *bp) in can_co_exist()
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()
[all …]
/Linux-v5.15/Documentation/powerpc/
Dptrace.rst53 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..
Ddawr-power9.rst80 PTRACE_GETHWDBGINFO) and setting the breakpoint, userspace will get an
/Linux-v5.15/scripts/gdb/linux/
Dsymbols.py68 breakpoint = None variable in LxSymbols
178 if self.breakpoint is not None:
179 self.breakpoint.delete()
180 self.breakpoint = None
181 self.breakpoint = LoadModuleBreakpoint(
/Linux-v5.15/arch/sh/include/asm/
Dtraps.h12 BUILD_TRAP_HANDLER(breakpoint);
/Linux-v5.15/Documentation/dev-tools/
Dgdb-kernel-debugging.rst83 - 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::
Dkgdb.rst582 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-v5.15/kernel/debug/kdb/
Dkdb_cmds5 # be safe. Global breakpoint commands affect each cpu as it is booted.
/Linux-v5.15/Documentation/trace/
Dkprobes.rst31 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 …]
Dftrace-uses.rst107 to the pt_regs structure like it would be if an breakpoint was placed
/Linux-v5.15/Documentation/virt/kvm/
Ds390-diag.rst80 DIAGNOSE function code 'X'501 - KVM breakpoint
83 If the function code specifies 0x501, breakpoint functions may be performed.
/Linux-v5.15/lib/
DKconfig.kgdb87 This will add an extra call back to kgdb for the breakpoint
113 0x0040 - allow flow control management (breakpoint, single step)
/Linux-v5.15/arch/sh/kernel/
Dhw_breakpoint.c358 BUILD_TRAP_HANDLER(breakpoint) in BUILD_TRAP_HANDLER() argument
/Linux-v5.15/samples/
DKconfig62 tristate "Build kernel hardware breakpoint examples -- loadable module only"
65 This builds kernel hardware breakpoint example modules.
/Linux-v5.15/Documentation/networking/
Dtproxy.rst80 https://git.breakpoint.cc/cgit/fw/tcprdr.git/
Dfilter.rst449 * 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-v5.15/Documentation/input/devices/
Datarikbd.rst170 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.15/drivers/scsi/hisi_sas/
Dhisi_sas.h451 struct hisi_sas_breakpoint *breakpoint; member
Dhisi_sas_main.c2350 memset(hisi_hba->breakpoint, 0, s); in hisi_sas_init_mem()
2463 hisi_hba->breakpoint = dmam_alloc_coherent(dev, s, in hisi_sas_alloc()
2466 if (!hisi_hba->breakpoint) in hisi_sas_alloc()
/Linux-v5.15/arch/arm/kernel/
Dtraps.c599 case NR(breakpoint): /* SWI BREAK_POINT */ in arm_syscall()
/Linux-v5.15/arch/xtensa/
DKconfig492 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-v5.15/Documentation/ia64/
Dfsys.rst216 breakpoint that triggers at any privilege level other than
/Linux-v5.15/tools/perf/Documentation/
Dperf-record.txt90 - 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-v5.15/Documentation/livepatch/
Dlivepatch.rst31 putting a breakpoint instruction instead of any instruction.
/Linux-v5.15/kernel/trace/
DKconfig618 If kprobes can use ftrace instead of breakpoint, ftrace related

12