From 633006926fd26eba7116526c760d2ab7d2a55fe3 Mon Sep 17 00:00:00 2001 From: Liav A Date: Thu, 12 Jan 2023 22:06:51 +0200 Subject: Kernel: Make the Jails' internal design a lot more sane This is done with 2 major steps: 1. Remove JailManagement singleton and use a structure that resembles what we have with the Process object. This is required later for the second step in this commit, but on its own, is a major change that removes this clunky singleton that had no real usage by itself. 2. Use IntrusiveLists to keep references to Process objects in the same Jail so it will be much more straightforward to iterate on this kind of objects when needed. Previously we locked the entire Process list and we did a simple pointer comparison to check if the checked Process we iterate on is in the same Jail or not, which required taking multiple Spinlocks in a very clumsy and heavyweight way. --- Kernel/CMakeLists.txt | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) (limited to 'Kernel/CMakeLists.txt') diff --git a/Kernel/CMakeLists.txt b/Kernel/CMakeLists.txt index f880747190..7168aa494e 100644 --- a/Kernel/CMakeLists.txt +++ b/Kernel/CMakeLists.txt @@ -93,7 +93,6 @@ set(KERNEL_SOURCES Graphics/VirtIOGPU/GraphicsAdapter.cpp IOWindow.cpp Jail.cpp - JailManagement.cpp SanCov.cpp Storage/ATA/AHCI/Controller.cpp Storage/ATA/AHCI/Port.cpp @@ -256,6 +255,7 @@ set(KERNEL_SOURCES PerformanceEventBuffer.cpp Process.cpp ProcessGroup.cpp + ProcessList.cpp Random.cpp Scheduler.cpp ScopedCritical.cpp -- cgit v1.2.3