Difference between revisions of "KBlockInfo"
Jump to navigation
Jump to search
(Created page with "Category:Kernel objects Size : 0x8 bytes {| class="wikitable" border="1" |- ! Offset ! Type ! Description |- | 0x0 | | |}") |
|||
| Line 11: | Line 11: | ||
|- | |- | ||
| 0x0 | | 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 KBlockInfo objects for (in order) .text pointer and page count, .rodata pointer and page count, and .data pointer and page count. | ||
Revision as of 20:02, 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 KBlockInfo objects for (in order) .text pointer and page count, .rodata pointer and page count, and .data pointer and page count.