Difference between revisions of "KBlockInfo"
Jump to navigation
Jump to search
| Line 19: | Line 19: | ||
|} | |} | ||
| − | KBlockInfo objects start with the FS KProcess on the kernel heap and continue in order. Each KProcess gets 3 KBlockInfo objects for (in order) .text pointer and page count, .rodata pointer and page count, and .data pointer and page count. | + | KBlockInfo objects start with the FS KProcess on the kernel heap and continue in order. Each KProcess gets 3 or more KBlockInfo objects for (in order) .text pointer and page count, .rodata pointer and page count, and .data pointer and page count. Apps that require more space than is available in a given block will get multiple KBlockInfo objects for each section to split it up into open spaces. |
Revision as of 20:40, 4 January 2015
Size : 0x8 bytes
| Offset | Type | Description |
|---|---|---|
| 0x0 | u32 | Pointer to memory section start in FCRAM using kernel vmem addresses |
| 0x4 | u32 | Page count |
KBlockInfo objects start with the FS KProcess on the kernel heap and continue in order. Each KProcess gets 3 or more KBlockInfo objects for (in order) .text pointer and page count, .rodata pointer and page count, and .data pointer and page count. Apps that require more space than is available in a given block will get multiple KBlockInfo objects for each section to split it up into open spaces.