lots of malloc(M_WAITOK)'s in interrupt context from camisr

[Andrew Gallatin]

John Baldwin writes:

 > If you need to do more work in your interrupt routine than just wakeups
 > and dinking with registers, you can always wake up a software interrupt
 > handler or some other random kthread to do things that take a long amount

Dumb question: Exactly what is one allowed to do in an INTR_FAST
interrupt context?  Obviously, you can't sleep.  But can you call
wakeup()?

Drew