| 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: Thu, 25 Oct 2007 15:52:28 -0700 From: Tim Bird <tim.bird@...sony.com> To: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca> CC: linux kernel <linux-kernel@...r.kernel.org>, Ingo Molnar <mingo@...hat.com>, Jon Smirl <jonsmirl@...oo.com>, Matt Mackall <mpm@...enic.com> Subject: Re: IRQ off latency of printk is very high Mathieu Desnoyers wrote: > It might help to read this thread I posted on LKML in January 2006 > explaining the problem, which led to some discussion about the issue. > > http://lkml.org/lkml/2006/6/3/48 This is very helpful. Jon Smirl's answer seems to give the rationale for supporting printk output in interrupt context. I'm not sure, however, if extending the interrupt off period to cover the console output is required. It didn't until Ingo changed it in 2.6.17. Maybe this was intentional to allow printk output to drain before another (printk in interrupt context) could even possibly be generated, but it seems like overkill. I'll continue looking at this. It helps a lot to know about the issues discussed in the prior thread. Thanks, -- Tim ============================= Tim Bird Architecture Group Chair, CE Linux Forum Senior Staff Engineer, Sony Corporation of America ============================= - 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