From: Pavel Machek <pavel@ucw.cz>
To: Huang Ying <ying.huang@intel.com>
Cc: lenb@kernel.org,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Andi Kleen <ak@linux.intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/5 -v2] acpi, apei, APEI supporting infrastructure
Date: Fri, 18 Dec 2009 19:11:23 +0100 [thread overview]
Message-ID: <20091218181123.GA1470@ucw.cz> (raw)
In-Reply-To: <1260429417.15264.394.camel@yhuang-dev.sh.intel.com>
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
next prev parent reply other threads:[~2009-12-18 18:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 7:16 [PATCH 2/5 -v2] acpi, apei, APEI supporting infrastructure Huang Ying
2009-12-18 18:11 ` Pavel Machek [this message]
2009-12-20 18:57 ` Andi Kleen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20091218181123.GA1470@ucw.cz \
--to=pavel@ucw.cz \
--cc=ak@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ying.huang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox