From: Andi Kleen <ak@linux.intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Huang Ying <ying.huang@intel.com>,
lenb@kernel.org,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 2/5 -v2] acpi, apei, APEI supporting infrastructure
Date: Sun, 20 Dec 2009 19:57:01 +0100 [thread overview]
Message-ID: <4B2E737D.2060902@linux.intel.com> (raw)
In-Reply-To: <20091218181123.GA1470@ucw.cz>
>
> Does this mean we'll now try to run acpi interrpretter from NMI
> context?
No. They have a very minimal interpreter for an own very simple byte code.
That code is NMI safe.
-Andi
prev parent reply other threads:[~2009-12-20 18:57 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
2009-12-20 18:57 ` Andi Kleen [this message]
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=4B2E737D.2060902@linux.intel.com \
--to=ak@linux.intel.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--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