ladybird/Kernel/Locking
kleines Filmröllchen d0e614c045 Kernel: Don't check that interrupts are enabled during early boot
The interrupts enabled check in the Kernel mutex is there so that we
don't lock mutexes within a spinlock, because mutexes reenable
interrupts and that will mess up the spinlock in more ways than one if
the thread moves processors. This check is guarded behind a debug flag
because it's too hard to fix all the problems at once, but we regressed
and weren't even getting to init stage 2 with it enabled. With this
commit, we get to stage 2 again. In early boot, there are no interrupts
enabled and spinlocks used, so we can sort of kind of safely ignore the
interrupt state. There might be a better solution with another boot
state flag that checks whether APs are up (because they have interrupts
enabled from the start) but that seems overkill.
2022-07-19 12:12:13 +01:00
..
LockLocation.h Kernel: Add missing includes in Locking 2021-12-15 23:34:11 -08:00
LockMode.h Kernel: Add missing includes in Locking 2021-12-15 23:34:11 -08:00
LockRank.cpp Kernel: Add implied auto-specifiers in Locking 2021-12-15 23:34:11 -08:00
LockRank.h Kernel: Fix a typo in LockRank::Process's comment 2021-09-08 19:17:07 +03:00
Mutex.cpp Kernel: Don't check that interrupts are enabled during early boot 2022-07-19 12:12:13 +01:00
Mutex.h Kernel: Track big lock blocked threads in separate list 2022-04-06 18:27:19 +02:00
MutexProtected.h Everywhere: Run clang-format 2022-04-01 21:24:45 +01:00
Spinlock.h Kernel: Move spinlock into Arch 2021-10-15 21:48:45 +01:00
SpinlockProtected.h Everywhere: Run clang-format 2022-04-01 21:24:45 +01:00