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: Tue, 10 Mar 2009 04:49:39 +0100 From: Andi Kleen <andi@...stfloor.org> To: Chris Friesen <cfriesen@...tel.com> Cc: linux-kernel@...r.kernel.org, Andi Kleen <andi@...stfloor.org>, Ingo Molnar <mingo@...e.hu> Subject: Re: reason for delay in arch/x86/kernel/traps.c::io_check_error()? On Mon, Mar 09, 2009 at 01:33:44PM -0600, Chris Friesen wrote: > > Hi all, > > I was just wondering about the basis for the delay in io_check_error(). > The ICH7 manual doesn't have any mention of a delay being required > here--is it necessary for other hardware, something not mentioned in the > manual, or just an accident? The complete NMI error logging handling does not really apply to any modern chipset; it's for ancient hardware (286, 386 generation). Those often needed strange delays too. -Andi -- ak@...ux.intel.com -- Speaking for myself only. -- 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