Lines Matching full:code
18 Non-instrumentable code - noinstr
22 for entry code before RCU starts watching and exit code after RCU stops
24 which means that (for example) a breakpoint in the breakpoint entry code would
27 Such code must be marked with the 'noinstr' attribute, placing that code into a
31 instrumentable ranges of code:
33 .. code-block:: c
41 handle_context(); // <-- instrumentable code
55 All non-instrumentable entry/exit code sections before and after the RCU
61 Syscall-entry code starts in assembly code and calls out into low-level C code
63 low-level C code must not be instrumented. A typical syscall handling function
64 invoked from low-level assembly code looks like this:
66 .. code-block:: c
90 function can be invoked. The instrumentable code section then ends, after which
103 available as fine grained subfunctions in cases where the architecture code
146 .. code-block:: c
177 code to be traced, while also maintaining symmetry with irq_exit_rcu() and
179 is that the early entry code up to irq_enter_rcu() must be aware that the
193 Interrupt entry/exit code doesn't strictly need to handle reentrancy, since it
195 the entry code is shared between the two.
206 in kernel mode (code patching). From user-space, they are treated like
229 Architecture-specific code looks like this:
231 .. code-block:: c
247 .. code-block:: c
278 while handling an NMI. So NMI entry code has to be reentrant and state updates