Don't spin in pause() during early boot for kthreads other than thread0.
pause() uses a spin loop to simulate a sleep during early boot. However, we only need this for thread0 to get far enough in the boot process to enable timers (at which point pause() can sleep). For other kthreads, sleeping in pause() is ok as the callout will be scheduled and will eventually fire once thread0 initializes timers. Tested by: Steven Kargl Sleuthing by: markj MFC after: 1 week Sponsored by: Netflix
This commit is contained in:
parent
46ac5f081d
commit
99bc7e4123
@ -321,7 +321,8 @@ pause_sbt(const char *wmesg, sbintime_t sbt, sbintime_t pr, int flags)
|
||||
if (sbt == 0)
|
||||
sbt = tick_sbt;
|
||||
|
||||
if (cold || kdb_active || SCHEDULER_STOPPED()) {
|
||||
if ((cold && curthread == &thread0) || kdb_active ||
|
||||
SCHEDULER_STOPPED()) {
|
||||
/*
|
||||
* We delay one second at a time to avoid overflowing the
|
||||
* system specific DELAY() function(s):
|
||||
|
Loading…
Reference in New Issue
Block a user