From: Huang Ying <ying.huang@intel.com>
To: lenb@kernel.org
Cc: linux-kernel@vger.kernel.org, ying.huang@intel.com,
andi@firstfloor.org, linux-acpi@vger.kernel.org
Subject: ACPI, APEI support
Date: Tue, 27 Apr 2010 14:41:09 +0800 [thread overview]
Message-ID: <1272350481-27951-1-git-send-email-ying.huang@intel.com> (raw)
This patchset adds the APEI (ACPI Platform Error Interface) support to
Linux kernel.
01-06 include the basic APEI HEST parsing and EINJ support. They have
been posted to mailing list before and get some reviews and
ACKs. Changes since the last post are as follow.
- Make APEI infrastructure and HEST parsing configurable built-in
instead of modules to solve some dependency issues.
- Some minor fixes, such as printk
07-10 are newly added to support GHES (Generic Hardware Error Source)
corrected memory error. On some machines, Machine Check can not report
physical address for some corrected memory errors, but GHES can do
that. So this simplified GHES is implemented and posted firstly.
11-12 are newly added to support using ERST for persistent storage of
MCE. This can improve fatal MCE report.
[PATCH 01/12] ACPI, IO memory pre-mapping and atomic accessing
[PATCH 02/12] ACPI, APEI, APEI supporting infrastructure
[PATCH 03/12] ACPI, APEI, HEST table parsing
[PATCH 04/12] ACPI, APEI, EINJ support
[PATCH 05/12] ACPI, APEI, Document for APEI
[PATCH 06/12] ACPI, APEI, PCIE AER, use general HEST table parsing in AER firmware_first setup
[PATCH 07/12] ACPI Hardware Error Device (PNP0C33) support
[PATCH 08/12] Unified UUID/GUID definition
[PATCH 09/12] ACPI, APEI, UEFI Common Platform Error Record (CPER) header
[PATCH 10/12] ACPI, APEI, Generic Hardware Error Source memory error support
[PATCH 11/12] ACPI, APEI, Error Record Serialization Table (ERST) support
[PATCH 12/12] ACPI, APEI, Use ERST for persistent storage of MCE
next reply other threads:[~2010-04-27 6:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-27 6:41 Huang Ying [this message]
2010-04-27 6:41 ` [PATCH 01/12] ACPI, IO memory pre-mapping and atomic accessing Huang Ying
2010-04-27 6:41 ` [PATCH 02/12] ACPI, APEI, APEI supporting infrastructure Huang Ying
2010-04-27 6:41 ` [PATCH 03/12] ACPI, APEI, HEST table parsing Huang Ying
2010-04-27 6:41 ` [PATCH 04/12] ACPI, APEI, EINJ support Huang Ying
2010-04-27 6:41 ` [PATCH 05/12] ACPI, APEI, Document for APEI Huang Ying
2010-04-27 6:41 ` [PATCH 06/12] ACPI, APEI, PCIE AER, use general HEST table parsing in AER firmware_first setup Huang Ying
2010-04-27 6:41 ` [PATCH 07/12] ACPI Hardware Error Device (PNP0C33) support Huang Ying
2010-04-27 6:41 ` [PATCH 08/12] Unified UUID/GUID definition Huang Ying
2010-04-27 6:41 ` [PATCH 09/12] ACPI, APEI, UEFI Common Platform Error Record (CPER) header Huang Ying
2010-04-27 6:41 ` [PATCH 10/12] ACPI, APEI, Generic Hardware Error Source memory error support Huang Ying
2010-04-27 6:41 ` [PATCH 11/12] ACPI, APEI, Error Record Serialization Table (ERST) support Huang Ying
2010-04-27 6:41 ` [PATCH 12/12] ACPI, APEI, Use ERST for persistent storage of MCE Huang Ying
2010-05-11 11:25 ` ACPI, APEI support 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=1272350481-27951-1-git-send-email-ying.huang@intel.com \
--to=ying.huang@intel.com \
--cc=andi@firstfloor.org \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).