Lines Matching full:code

18 Existing stacktrace code may not always give an accurate picture of all
36   return code is zero to indicate that the trace is reliable.
38 * The return code is non-zero to indicate that the trace is not reliable.
48 code, and should not get stuck in an infinite loop or access memory in
55 To ensure that kernel code can be correctly unwound in all cases,
56 architectures may need to verify that code has been compiled in a manner
84 * Dynamically generated code (e.g. eBPF) or foreign code (e.g. EFI runtime
98 4.2 Identifying unwindable code
101 Unwinding typically relies on code following specific conventions (e.g.
102 manipulating a frame pointer), but there can be code which may not follow these
111 * Dynamically generated code (e.g. eBPF, optprobe trampolines).
113 * Foreign code (e.g. EFI runtime services).
116 trace, it is strongly recommended that architectures positively identify code
118 other code.
120 Kernel code including modules and eBPF can be distinguished from foreign code
124 There are several ways an architecture may identify kernel code which is deemed
127 * Placing such code into special linker sections, and rejecting unwinding from
128   any code in these sections.
130 * Identifying specific portions of code using bounds information.
183 .. code-block:: none
239 .. code-block:: none
266 .. code-block:: none
291 .. code-block:: none