svn commit: r192604 - in user/kmacy/releng_7_2_fcs/sys: dev/hwpmc sys

[Kip Macy]

ter.
>
> Umm, that doesn't help.  Your kthread's main routine is "physically" located
> in your kld.  It needs to get into the text of kthread_exit() before it is
> safe for your module to unload, and so you have to sleep on the kthread/kproc
> pointer to wait for the wakeup in kthread_exit() to fire.  You could have
> easily used msleep_spin() for this w/o hacking up condvar's to support spin
> locks too, FWIW.
>

Good point.

Which gets to my next question. Why is condvar preferred to msleep /
wakeup for everything BUT spin locks? This seems a bit hackish.

Thanks,
Kip