Lines Matching full:architectures

20 debugging are unsound for livepatching. Livepatching depends on architectures
28 Architectures must implement one of the reliable stacktrace functions.
29 Architectures using CONFIG_ARCH_STACKWALK must implement
30 'arch_stack_walk_reliable', and other architectures must implement
56 architectures may need to verify that code has been compiled in a manner
59 functions use specific prologue and epilogue sequences. Architectures
71 The unwinding process varies across architectures, their respective procedure
73 details that architectures should consider.
89 architectures verify that a stacktrace ends at an expected location, e.g.
116 trace, it is strongly recommended that architectures positively identify code
140 For some architectures this may change at runtime as a result of dynamic
148 Architectures which cannot identify when it is reliable to unwind such cases
154 Architectures which can identify when it is reliable to unwind such cases (or
215 Architectures might not always be able to unwind such sequences, such as when
219 It is recommended that architectures unwind cases where return_to_handler has
220 not yet been returned to, but architectures are not required to unwind from the
221 middle of return_to_handler and can report this as unreliable. Architectures
249 Architectures must either ensure that unwinders either reliably unwind
255 On some other architectures, 'call' instructions place the return address into a
257 link register without modifying the register. On these architectures software
306 link register value at a function call boundary. Architectures where this is