RGBCube/serenity
1
Fork 0
mirror of https://github.com/RGBCube/serenity synced 2025-07-26 11:57:34 +00:00
Code Issues Activity Actions

Kernel: Don't wrap AddressSpace's RegionTree in SpinlockProtected

Browse source 
Now that AddressSpace itself is always SpinlockProtected, we don't
need to also wrap the RegionTree. Whoever has the AddressSpace locked
is free to poke around its tree.
This commit is contained in:
Andreas Kling 2022-08-23 20:30:12 +02:00
parent d3e8eb5918
commit da24a937f5
6 changed files with 212 additions and 265 deletions
Download patch file Download diff file Expand all files Collapse all files

10
Kernel/Memory/AddressSpace.h
View file

@ -27,8 +27,8 @@ public:
PageDirectory& page_directory() { return *m_page_directory; }
PageDirectory const& page_directory() const { return *m_page_directory; }
SpinlockProtected<RegionTree>& region_tree() { return m_region_tree; }
SpinlockProtected<RegionTree> const& region_tree() const { return m_region_tree; }
RegionTree& region_tree() { return m_region_tree; }
RegionTree const& region_tree() const { return m_region_tree; }
void dump_regions();
@ -66,11 +66,7 @@ private:
LockRefPtr<PageDirectory> m_page_directory;
// NOTE: The total range is also in the RegionTree, but since it never changes,
// it's nice to have it in a place where we can access it without locking.
VirtualRange m_total_range;
SpinlockProtected<RegionTree> m_region_tree;
RegionTree m_region_tree;
bool m_enforces_syscall_regions { false };
};