Kernel ABI: Difference between revisions
Specify GetSystemTick ABI |
GasInfinity (talk | contribs) document the calling convention of literally all syscalls |
||
Line 1: | Line 1: | ||
= Calling Convention = | |||
Seems to be [https://github.com/ARM-software/abi-aa/blob/main/aapcs32/aapcs32.rst#the-base-procedure-call-standard AAPCS]-based (with modifications) | |||
== Overview == | |||
=== Inputs === | |||
* <code>r0–r3</code> : Argument / Scratch registers (caller-saved), inherited from AAPCS. ''If an input is to be placed on the stack, it will instead use the next free register starting from <code>r0</code>.'' | |||
=== Outputs === | |||
* <code>r0-r1</code> : Result, inherited from AAPCS. ''If multiple outputs are returned (e.g., <code>ControlMemory</code>), they are placed in consecutive registers starting from <code>r0</code>.'' | |||
== Example == | |||
<code>Result ControlMemory(uintptr_t* out, uintptr_t addr0, uintptr_t addr1, size_t size, MemoryOperation operation, MemoryPermission permissions)</code> | |||
=== Inputs === | |||
Following standard [https://github.com/ARM-software/abi-aa/blob/main/aapcs32/aapcs32.rst#the-base-procedure-call-standard AAPCS] register selection: | |||
; <code>r1</code> -> addr0 | |||
; <code>r2</code> -> addr1 | |||
; <code>r3</code> -> size | |||
As there are still have more arguments, the next free registers are selected starting from <code>r0</code> | |||
; <code>r0</code> -> operation | |||
; <code>r4</code> -> permissions | |||
=== Outputs === | |||
; <code>r0</code> -> Result | |||
; <code>r1</code> -> uintptr_t out | |||
== System calls == | |||
{| class="wikitable" border="1" | {| class="wikitable" border="1" | ||
|- | |- |
Revision as of 22:01, 29 August 2025
Calling Convention
Seems to be AAPCS-based (with modifications)
Overview
Inputs
r0–r3
: Argument / Scratch registers (caller-saved), inherited from AAPCS. If an input is to be placed on the stack, it will instead use the next free register starting fromr0
.
Outputs
r0-r1
: Result, inherited from AAPCS. If multiple outputs are returned (e.g.,ControlMemory
), they are placed in consecutive registers starting fromr0
.
Example
Result ControlMemory(uintptr_t* out, uintptr_t addr0, uintptr_t addr1, size_t size, MemoryOperation operation, MemoryPermission permissions)
Inputs
Following standard AAPCS register selection:
r1
-> addr0r2
-> addr1r3
-> size
As there are still have more arguments, the next free registers are selected starting from r0
r0
-> operationr4
-> permissions
Outputs
r0
-> Resultr1
-> uintptr_t out
System calls
ID | Name | Inputs | Outputs |
---|---|---|---|
0x01 | ControlMemory |
|
|
0x02 | QueryMemory |
|
|
0x03 | ExitProcess | None | None, doesn't return |
0x04 | GetProcessAffinityMask |
|
|
0x05 | SetProcessAffinityMask |
|
|
0x06 | GetProcessIdealProcessor |
|
|
0x07 | SetProcessIdealProcessor |
|
|
0x08 | CreateThread |
|
|
0x09 | ExitThread | None | None, doesn't return |
0x0A | SleepThread |
|
None |
0x0B | GetThreadPriority |
|
|
0x0C | SetThreadPriority |
|
|
0x0D | GetThreadAffinityMask |
|
|
0x0E | SetThreadAffinityMask |
|
|
0x0F | GetThreadIdealProcessor |
|
|
0x10 | SetThreadIdealProcessor |
|
|
0x11 | GetProcessorID |
None |
|
0x24 | WaitSynchronization1 |
|
|
0x1B | SetTimer | Timer handle, initial_low, interval_low, initial_high, interval_high | Result |
0x28 | GetSystemTick | None |
|
0x2D | ConnectToPort | ??r1 : pointer to port name
|
r0 : Result r1 : handle to KClientSession
|
0x32 | SendSyncRequest | r0 : handle to KClientSession
|
r0 : Result |