RGBCube/serenity
1
Fork 0
mirror of https://github.com/RGBCube/serenity synced 2025-05-23 18:35:07 +00:00
Code Issues Activity Actions

Kernel: Fix Thread::relock_process leaving critical section

Browse source 
We don't want to explicitly enable interrupts when leaving the
critical section to trigger a context switch.
This commit is contained in:
Tom 2021-01-23 22:41:44 -07:00 • committed by Andreas Kling
parent ccaeb47401
commit e9e76b8074
2 changed files with 11 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

11
Kernel/Thread.cpp
View file

@ -305,17 +305,16 @@ void Thread::relock_process(LockMode previous_locked, u32 lock_count_to_restore)
// flagged by calling Scheduler::donate_to or Scheduler::yield
// above. We have to do it this way because we intentionally
// leave the critical section here to be able to switch contexts.
u32 prev_flags;
u32 prev_crit = Processor::current().clear_critical(prev_flags, true);
auto critical_before = Processor::current().in_critical();
ASSERT(critical_before);
// CONTEXT SWITCH HAPPENS HERE!
// NOTE: We may be on a different CPU now!
Processor::current().restore_critical(prev_crit, prev_flags);
Scheduler::yield_from_critical();
ASSERT(Processor::current().in_critical() == critical_before);
if (previous_locked != LockMode::Unlocked) {
// We've unblocked, relock the process if needed and carry on.
RESTORE_LOCK(process().big_lock(), previous_locked, lock_count_to_restore);
ASSERT(Processor::current().in_critical() == critical_before);
}
}