2.0.0: Difference between revisions

Line 105:

* Kernel stacks are now allocated with a slabheap.

* ~~While~~ 1.0.0 ~~had two~~ pools ~~with size 0~~, ~~now~~ it ~~uses all three~~. ~~The last one size is calculated dynamically to fit all the built-in sysmodules,~~ and ~~it's~~ now protected by the kernel carveout.

* KHeapArrange was changed. On 1.0.0 it held address/size for three pools ("base", "application", "system") and application/system were zero-sized/unused. Now it holds "pool management", "secure", "non-secure". Pool management and secure are now protected by the kernel carveout.

** Secure pool size is dynamically calculated as size of all kips (including stacks) + 24 MB (FS sysmodule heap) + 1 MB (spare pages for e.g. IPC buffer usage).

** If only one KIP is present, all memory goes to secure pool and non-secure pool does not exist.

@@ Line 105: / Line 105: @@
 * Kernel stacks are now allocated with a slabheap.
-* While 1.0.0 had two pools with size 0, now it uses all three. The last one size is calculated dynamically to fit all the built-in sysmodules, and it's now protected by the kernel carveout.
+* KHeapArrange was changed. On 1.0.0 it held address/size for three pools ("base", "application", "system") and application/system were zero-sized/unused. Now it holds "pool management", "secure", "non-secure". Pool management and secure are now protected by the kernel carveout.
+** Secure pool size is dynamically calculated as size of all kips (including stacks) + 24 MB (FS sysmodule heap) + 1 MB (spare pages for e.g. IPC buffer usage).
+** If only one KIP is present, all memory goes to secure pool and non-secure pool does not exist.
 {{NavboxVersions}}