[PATCH -v5 00/14] ACPI, APEI support

[Huang Ying]

This patchset adds the APEI (ACPI Platform Error Interface) support to
Linux kernel.

Changelog:

v5:

- Incorporate some fixes to previous version

- Add EINJ parameter support: 13, 14

v4:

1-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 -v5 01/14] ACPI, IO memory pre-mapping and atomic accessing
[PATCH -v5 02/14] ACPI, APEI, APEI supporting infrastructure
[PATCH -v5 03/14] ACPI, APEI, HEST table parsing
[PATCH -v5 04/14] ACPI, APEI, EINJ support
[PATCH -v5 05/14] ACPI, APEI, Document for APEI
[PATCH -v5 06/14] ACPI, APEI, PCIE AER, use general HEST table parsing in AER firmware_first setup
[PATCH -v5 07/14] ACPI Hardware Error Device (PNP0C33) support
[PATCH -v5 08/14] Unified UUID/GUID definition
[PATCH -v5 09/14] ACPI, APEI, UEFI Common Platform Error Record (CPER) header
[PATCH -v5 10/14] ACPI, APEI, Generic Hardware Error Source memory error support
[PATCH -v5 11/14] ACPI, APEI, Error Record Serialization Table (ERST) support
[PATCH -v5 12/14] ACPI, APEI, Use ERST for persistent storage of MCE
[PATCH -v5 13/14] Add x64 support to debugfs
[PATCH -v5 14/14] ACPI, APEI, EINJ injection parameters support
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/