Steven Rostedt wrote:
On Mon, 2009-10-26 at 08:02 +0100, Andi Kleen wrote:
Also more work could be done to make CPU boot up less verbose without
sacrifying debuggability if something goes wrong.
What about moving printks over to trace_printk or something. And that
way we can have a "boot up" ring buffer that can later be retrieved if
something goes wrong. It already dumps to the console on panic/oops.
The trace_printk will be hidden and is very fast.
-- Steve
I haven't heard of "trace_printk" but how does this differ from the
existing kernel log buffer you get with 'dmesg'?
Thanks,
Mike
--
To unsubscribe from this list: send the line "unsubscribe linux-doc" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
