mirror of
https://github.com/RGBCube/serenity
synced 2025-05-31 07:38:10 +00:00
Kernel: Fix boot profiling after big process lock separation regression
When I laid down the foundation for the start of the big process lock separation, I added asserts to all system call implementations to validate we hold the big process lock in the locations we think we should be. Adding that assert to sys$profiling_enable broke boot time profiling as we were never holding the lock on boot. Even though it's not technically required, lets make sure to hold the lock while enabling to appease the assert.
This commit is contained in:
parent
58fb38551c
commit
d496eb48e3
1 changed files with 1 additions and 0 deletions
|
@ -355,6 +355,7 @@ void init_stage2(void*)
|
|||
|
||||
if (boot_profiling) {
|
||||
dbgln("Starting full system boot profiling");
|
||||
MutexLocker mutex_locker(Process::current()->big_lock());
|
||||
auto result = Process::current()->sys$profiling_enable(-1, ~0ull);
|
||||
VERIFY(!result.is_error());
|
||||
}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue