On Sat, Sep 20, 2014 at 09:10:47AM -0700, Joe Perches wrote: > On Sat, 2014-09-20 at 17:47 +0200, Peter Zijlstra wrote: > > On a whole, printk() is entirely useless for debugging these days, its > > far too fragile/unreliable to be taken seriously so I really don't care > > on that point either. > > That's unfortunate. > > Care to enumerate the issues that you believe make > printk too fragile/unreliable for debugging?
Look at what it takes to end up at console->write(), and then realize that some console implementations require scheduling and other nonsense to actually implement ->write(). The (only) reliable option is early_printk() with the early_serial_console driver. The rest is useless crap these days. -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
