lists.openwall.net | 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
| ||
|
Date: Mon, 26 Oct 2009 11:05:07 -0700 From: Mike Travis <travis@....com> To: rostedt@...dmis.org CC: Andi Kleen <andi@...stfloor.org>, Ingo Molnar <mingo@...e.hu>, Thomas Gleixner <tglx@...utronix.de>, Andrew Morton <akpm@...ux-foundation.org>, Jack Steiner <steiner@....com>, Randy Dunlap <rdunlap@...otime.net>, Greg Kroah-Hartman <gregkh@...e.de>, Frederic Weisbecker <fweisbec@...il.com>, Heiko Carstens <heiko.carstens@...ibm.com>, Robin Getz <rgetz@...log.com>, Dave Young <hidave.darkstar@...il.com>, linux-kernel@...r.kernel.org, linux-doc@...r.kernel.org 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'? Thanks, Mike -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists