Searched refs:epilogue (Results 1 – 8 of 8) sorted by relevance
| /linux-6.15/Documentation/arch/arm64/ |
| H A D | mops.rst | 8 instructions: a prologue, main and epilogue (for example: CPYP, CPYM, CPYE).
10 A main or epilogue instruction can take a MOPS exception for various reasons,
|
| /linux-6.15/Documentation/livepatch/ |
| H A D | reliable-stacktrace.rst | 59 functions use specific prologue and epilogue sequences. Architectures
138 epilogue a frame pointer may be transiently invalid, or during the function
|
| /linux-6.15/Documentation/bpf/ |
| H A D | bpf_design_QA.rst | 143 Q: Why BPF has implicit prologue and epilogue?
149 of LD_ABS insn). Those instructions need to invoke epilogue and
|
| H A D | classic_vs_extended.rst | 187 Prologue and epilogue are emitted by JIT and are implicit in the
|
| /linux-6.15/arch/arc/ |
| H A D | Kconfig | 147 * Function prologue/epilogue: ENTER_S, LEAVE_S
|
| /linux-6.15/Documentation/trace/ |
| H A D | ftrace-design.rst | 184 code. Since you are returning from a function (after the epilogue), you might
|
| /linux-6.15/arch/arm/crypto/ |
| H A D | sha1-armv4-large.S | 41 @ performance is affected by prologue and epilogue overhead,
|
| /linux-6.15/net/ceph/ |
| H A D | messenger_v2.c | 1004 void *epilogue, struct page **pages, int dpos, in setup_message_sgs() argument
1055 sg_set_buf(cur_sg, epilogue, in setup_message_sgs()
|