Lines Matching full:may

15 functions may have live state and therefore may not be safe to patch. One way
18 Existing stacktrace code may not always give an accurate picture of all
35 * The trace includes all functions that the task may be returned to, and the
56 architectures may need to verify that code has been compiled in a manner
57 expected by the unwinder. For example, an unwinder may expect that
63 In some cases, an unwinder may require metadata to correctly unwind.
78 Unwinding may terminate early for a number of reasons, including:
102 manipulating a frame pointer), but there can be code which may not follow these
103 conventions and may require special handling in the unwinder, e.g.
124 There are several ways an architecture may identify kernel code which is deemed
136 in a consistent state suitable for reliable unwinding, but this may not be the
138 epilogue a frame pointer may be transiently invalid, or during the function
139 body the return address may be held in an arbitrary general purpose register.
140 For some architectures this may change at runtime as a result of dynamic
144 state is in an inconsistent state, it may not be possible to reliably unwind,
145 and it may not be possible to identify whether such unwinding will be reliable.
150 boundaries. Note that it may be reliable to unwind across certain
165 * An ftrace trampoline may modify the return address so that function graph
168 * A kprobes (or optprobes) trampoline may modify the return address so that
174 is altered by the trampoline, the unwinder may report the original return
259 the duration of a function call, the return address may be held in the link
279 describe this function's return address. A trace at this point may describe
281 may consume two entries from the fgraph return stack rather than one entry.
289 Similarly, a function may deliberately clobber the LR, e.g.
305 Due to cases such as the above, it may only be possible to reliably consume a