You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Don't store idle tasks on each runqueue (theseus-os#982)
* As part of our ongoing scheduler/runqueue redesign,
there is no real reason to store each CPU's idle task
in a scheduler runqueue. They are only used separately
as a "last resort" when no runnable tasks exist, so we
can store them alongside the runqueue rather than inside it.
* Also, we change the creation of idle tasks to be done
as part of initializing the tasking subsystem on each CPU
rather than as an explicit step in the captain's init routine.
* In the future, each CPU's idle task can be stored in
CPU-local storage, since they ideologically "belong" to
a CPU instance rather than a runqueue instance.
* Unrelated: move `state_transfer` to old crates, as it
currently doesn't build any more due to the ongoing
scheduler/runqueue changes.
Signed-off-by: Klimenty Tsoutsman <[email protected]>
0 commit comments