summaryrefslogtreecommitdiff
path: root/Kernel/VM/RangeAllocator.cpp
AgeCommit message (Collapse)Author
2019-09-30Kernel: Make it possible to turn off VM guard pages at compile timeAndreas Kling
This might be useful for debugging since guard pages introduce a fair amount of noise in the virtual address space.
2019-09-22Kernel: Pad virtual address space allocations with guard pagesAndreas Kling
Put one unused page on each side of VM allocations to make invalid accesses more likely to generate crashes. Note that we will not add this guard padding for mmap() at a specific memory address, only to "mmap it anywhere" requests.
2019-06-07Kernel: Rename LinearAddress => VirtualAddress.Andreas Kling
2019-06-07Kernel: Run clang-format on everything.Andreas Kling
2019-05-22Kernel: Forked children should inherit their RangeAllocator by copy.Andreas Kling
Otherwise we'll start handing out addresses that are very likely already in use by existing ranges.
2019-05-18Kernel: Remove some RangeAllocator debug spam.Andreas Kling
2019-05-17Kernel: Use a RangeAllocator for kernel-only virtual space allocation too.Andreas Kling
2019-05-17Kernel: Implement a simple virtual address range allocator.Andreas Kling
This replaces the previous virtual address allocator which was basically just "m_next_address += size;" With this in place, virtual addresses can get reused, which cuts down on the number of page tables created. When we implement ASLR some day, we'll probably have to do page table deallocation, but for now page tables are only deallocated once the process dies.