Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1751383AbWECWWm (ORCPT ); Wed, 3 May 2006 18:22:42 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1751384AbWECWWm (ORCPT ); Wed, 3 May 2006 18:22:42 -0400 Received: from 66.239.25.20.ptr.us.xo.net ([66.239.25.20]:55703 "EHLO zoot.lnxi.com") by vger.kernel.org with ESMTP id S1751383AbWECWWl (ORCPT ); Wed, 3 May 2006 18:22:41 -0400 Message-Id: <4458D8C60200003600006167@zoot.lnxi.com> X-Mailer: Novell GroupWise Internet Agent 7.0.1 Beta Date: Wed, 03 May 2006 16:22:30 -0600 From: "Doug Thompson" To: , Cc: , , , , , Subject: Re: Problems with EDAC coexisting with BIOS Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Content-Disposition: inline Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 964 Lines: 25 >>> Alan Cox 05/03/06 3:44 PM >>> On Mer, 2006-05-03 at 21:25 +0100, Tim Small wrote: >> something with NMI-signalled errors, I was wondering what the problems >> with using NMI-signalled ECC errors were? >The big problem with NMI is that it can occur *during* a PCI >configuration sequence (ie during pci_config_* functions). That means we >can't safely do some I/O, especially configuration space I/O in an NMI >handler. At best we could set a flag and catch it afterwards. Dave Peterson did submit a set of patches to provide a deferred calling mechanism triggered by the NMI handler. I am in the process of reading up on that patch. It currently is in the bluesmoke project. doug t - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/