KThreadContext: Difference between revisions
No edit summary |
No edit summary |
||
| (3 intermediate revisions by the same user not shown) | |||
| Line 33: | Line 33: | ||
| u32[4] | | u32[4] | ||
| SVC access control data copied from KThread's owner process | | SVC access control data copied from KThread's owner process | ||
|- | |||
| 0xF48 (page_end - 0xB8) | |||
| u8[4] | |||
| Debug info (read by the SVC handler): | |||
0: Bit0: reschedule. Bit1: switch context. If non zero, and depending on <code>currentThread->shallTerminate</code>, send thread exit debug events after handling valid/authorized SVCs (except 0xFF). Cleared to zero after handling. Bit2: lock debug features | |||
1: "Allow debug" flag from the process's exheader. If set, <code>{r0-r7, r12, lr_svc}</code> will be pushed (they'll always be when handling invalid/unauthorized SVCs/SVC 0xFF). Needed for svcGetThreadContext and svcSetThreadContext to work properly in contexts other than exception handling (incl. hardware breakpoints). If lr_svc is set to one in this frame, the registers are reloaded from it (used with svcBreak, svc 0xff, etc). | |||
2: ? | |||
3: ID of the SVC being handled (reset to 0 when done). | |||
|- | |- | ||
| 0xF50 (page_end - 0xB0) | | 0xF50 (page_end - 0xB0) | ||