lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  PHC 
Open Source and information security mailing list archives
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:	Mon, 26 Oct 2009 11:05:07 -0700
From:	Mike Travis <>
CC:	Andi Kleen <>, Ingo Molnar <>,
	Thomas Gleixner <>,
	Andrew Morton <>,
	Jack Steiner <>,
	Randy Dunlap <>,
	Greg Kroah-Hartman <>,
	Frederic Weisbecker <>,
	Heiko Carstens <>,
	Robin Getz <>,
	Dave Young <>,,
Subject: Re: [PATCH 1/8] SGI x86_64 UV: Add limit console output function

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'?


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

Powered by blists - more mailing lists