On 01 Oct 2009, at 8:47 PM, Ed Cashin wrote:
Jason Nymble <jason.nymble@xxxxxxxxx> writes:
Also, unless I'm mistaken, you can't/shouldn't call printk from
interrupt context?
Ooh. That would be inconvenient.
For examples of printk being called from interrupt context, look for
error handling around allocations with GFP_ATOMIC.
The comment above the definition of the printk function starts with,
/**
* printk - print a kernel message
* @fmt: format string
*
* This is printk(). It can be called from any context. We want it
to work.
Excellent, thanks for pointing that out! I have long lived under a
false idea of where one can use printk then...
--
To unsubscribe from this list: send an email with
"unsubscribe kernelnewbies" to ecartis@xxxxxxxxxxxx
Please read the FAQ at http://kernelnewbies.org/FAQ
