When kernel code is preempted in a user thread context (e.g. a syscall), the thread might have locked the scheduler
Possible solutions:
- Never preempt kernel code
- Put the scheduler in a spin mutex
When kernel code is preempted in a user thread context (e.g. a syscall), the thread might have locked the scheduler
Possible solutions:
- Never preempt kernel code
- Put the scheduler in a spin mutex
juju
added the BugQuestion labels 2023-01-06 17:41:21 +00:00
When kernel code is preempted in a user thread context (e.g. a syscall), the thread might have locked the scheduler
Possible solutions:
- Never preempt kernel code
- Put the scheduler in a spin mutex