SVC: Difference between revisions
No edit summary |
No edit summary |
||
| Line 333: | Line 333: | ||
Each process has a separate handle-table, the size of this table is stored in the exheader. The handles in a handle-table can't be used in the context of other processes, since those handles don't exist in other handle-tables. | Each process has a separate handle-table, the size of this table is stored in the exheader. The handles in a handle-table can't be used in the context of other processes, since those handles don't exist in other handle-tables. | ||
Calling svcBreak on retail will only terminate the process which called this SVC. | Calling svcBreak on retail will only terminate the process which called this SVC. Using CloseHandle() with a KThread handle will terminate the specified thread. | ||
ControlMemory and MapMemoryBlock can be used to map memory pages, these two SVCs only support mapping execute-never R/W pages. The input permissions parameter for these SVCs must be <=3, where value zero is used when un-mapping memory. Bitmask 0xf00 for ControlMemory parameter MemoryType is the memory-type, when this is zero the memory-type is loaded from the kernel flags stored in the exheader ARM11 kernel descriptors, for the process using the SVC. The low 8-bits are the type: 1 is for un-mapping memory, 3 for mapping memory. Addr1 is not used for type1 and type3. | ControlMemory and MapMemoryBlock can be used to map memory pages, these two SVCs only support mapping execute-never R/W pages. The input permissions parameter for these SVCs must be <=3, where value zero is used when un-mapping memory. Bitmask 0xf00 for ControlMemory parameter MemoryType is the memory-type, when this is zero the memory-type is loaded from the kernel flags stored in the exheader ARM11 kernel descriptors, for the process using the SVC. The low 8-bits are the type: 1 is for un-mapping memory, 3 for mapping memory. Addr1 is not used for type1 and type3. | ||