kernel - Fix panic when usched is used to force a cpu w/the dfly scheduler
authorMatthew Dillon <dillon@apollo.backplane.com>
Fri, 2 Aug 2013 17:46:40 +0000 (10:46 -0700)
committerMatthew Dillon <dillon@apollo.backplane.com>
Fri, 2 Aug 2013 17:46:40 +0000 (10:46 -0700)
commitd87af38ca063b9782ed8e05a68691890f58d489c
treebf608c18df94f6f77b1279b319d99548877e748b
parentf3ec743d786818511ddac033ed6a4a6260344b66
kernel - Fix panic when usched is used to force a cpu w/the dfly scheduler

* Fix a panic for 'usched dfly:0x1 sh', or other similar cpu forcing
  mechanic.

* The scheduler was not being notified of the forced migration which
  caused it to assert on a sanity check later on.  Add the needed
  infrastructure.

Reported-by: vsrinivas
sys/kern/usched_bsd4.c
sys/kern/usched_dfly.c
sys/kern/usched_dummy.c
sys/sys/usched.h