[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20091218181123.GA1470@ucw.cz>
Date: Fri, 18 Dec 2009 19:11:23 +0100
From: Pavel Machek <pavel@....cz>
To: Huang Ying <ying.huang@...el.com>
Cc: lenb@...nel.org,
ACPI Devel Maling List <linux-acpi@...r.kernel.org>,
Andi Kleen <ak@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 2/5 -v2] acpi, apei, APEI supporting infrastructure
On Thu 2009-12-10 15:16:57, Huang Ying wrote:
> APEI stands for ACPI Platform Error Interface, which allows to report
> errors (for example from the chipset) to the operating system. This
> improves NMI handling especially. In addition it supports error
> serialization and error injection.
>
> For more information about APEI, please refer to ACPI Specification
> version 4.0, chapter 17.
>
> This patch provides some common functions used by more than one APEI
> tables, mainly framework of interpreter for EINJ and ERST.
>
> A machine readable language is defined for EINJ and ERST for OS to
> execute, and so to drive the firmware to fulfill the corresponding
> functions. The machine language for EINJ and ERST is compatible, so a
> common framework is defined for them.
Does this mean we'll now try to run acpi interrpretter from NMI
context?
I don't see how that can work; NMI is really special...
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
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