| 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 linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Date: Mon, 6 Jun 2011 19:07:25 +0200 From: Ingo Molnar <mingo@...e.hu> To: Arne Jansen <lists@...-jansens.de> Cc: Peter Zijlstra <peterz@...radead.org>, Linus Torvalds <torvalds@...ux-foundation.org>, mingo@...hat.com, hpa@...or.com, linux-kernel@...r.kernel.org, efault@....de, npiggin@...nel.dk, akpm@...ux-foundation.org, frank.rowand@...sony.com, tglx@...utronix.de, linux-tip-commits@...r.kernel.org Subject: Re: [debug patch] printk: Add a printk killswitch to robustify NMI watchdog messages * Arne Jansen <lists@...-jansens.de> wrote: > > As long as it doesn't scramble the order of the messages, the > > delay imho doesn't matter even in very printk-heavy debugging > > sessions. > > And, as important, doesn't reduce the throughput of printk. Having > only 100 wakeups/s sounds like the throughput is limited to > 100xsizeof(ring buffer). Nah. I for example *always* kill klogd during such printk based debugging sessions, because it's *already* very easy to overflow its buffering abilities. Also, klogd often interferes with debugging. So i make the log buffer big enough to contain enough debugging info. So it's a non-issue IMHO. Linus, what do you think? Thanks, Ingo -- 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