console spin_lock
Quoted 6 lines · Andrew Morton
Assumption:
- Once the system is up and running, it's always safe to calldown()whenin_interrupt()returns false - probably not the case in parts of the exit path - tough.Anyway, that's the thoughtware. Sound sane?
Do not forget to handle printk() done by fbdev driver... It may invoke printk() from user context, but with console_semaphore already held... Something like reentrant_semaphore? Also, we should declare which console/fbdev function can printk/can schedule and which must not, as using interrupts & schedule could yield CPU to other tasks when (hardware assisted) operation is performed. Some of them (clear, bmove) can take loong time to finish.
Best regards,
Petr Vandrovec [email protected]
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected]
Please read the FAQ at http://www.tux.org/lkml/