| 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, 2 Mar 2009 23:35:26 +0000 From: Alan Cox <alan@...rguk.ukuu.org.uk> To: Peter Zijlstra <a.p.zijlstra@...llo.nl> Cc: David Brownell <david-b@...bell.net>, Thomas Gleixner <tglx@...utronix.de>, Andrew Morton <akpm@...ux-foundation.org>, me@...ipebalbi.com, linux-kernel@...r.kernel.org, linux-input@...r.kernel.org, felipe.balbi@...ia.com, dmitry.torokhov@...il.com, sameo@...nedhand.com Subject: Re: lockdep and threaded IRQs (was: ...) > Because running irq handlers with irqs enabled it plain silly. It makes enormous sense to run with the ability to mask *just* the IRQ that occurred and not others so that long lasting interrupts. There is another reason not to do this of course - the real time work makes it essentially irrelevant by doing the job right and reducing the entire problem space to software priority management. > Except it turns out there is some really broken ass hardware out there. > But supposedly IDE PIO could be done from a threaded handler. Only if you support reliable masking of a single IRQ *after* the IRQ handler returns. The real time patches can do that for some chipsets but on the PC at least you are into the realms of deepest darkest APIC weirdness and that requires Ingo's pointy hat and wand.. Alan -- 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