RGBCube/serenity
1
Fork 0
mirror of https://github.com/RGBCube/serenity synced 2025-06-01 08:28:11 +00:00
Code Issues Activity Actions

Kernel: Don't remap all regions from Region::remap_vmobject_page()

Browse source 
When handling a page fault, we only need to remap the faulting region in
the current process. There's no need to traverse *all* regions that map
the same VMObject and remap them cross-process as well.

Those other regions will get remapped lazily by their own page fault
handlers eventually. Or maybe they won't and we avoided some work. :^)
This commit is contained in:
Andreas Kling 2022-08-18 15:23:56 +02:00
parent 45e6123de8
commit 27c1135d30
2 changed files with 8 additions and 19 deletions
Download patch file Download diff file Expand all files Collapse all files

1
Kernel/Memory/Region.h
View file

@ -200,7 +200,6 @@ private:
Region(VirtualRange const&, NonnullRefPtr<VMObject>, size_t offset_in_vmobject, OwnPtr<KString>, Region::Access access, Cacheable, bool shared);
[[nodiscard]] bool remap_vmobject_page(size_t page_index, bool with_flush = true);
[[nodiscard]] bool do_remap_vmobject_page(size_t page_index, bool with_flush = true);
void set_access_bit(Access access, bool b)
{