Commit 112f1fc0 authored by Chen Gong's avatar Chen Gong Committed by Tony Luck

ACPI, APEI, EINJ: Add missed ACPI5 support for error trigger table

To handle error trigger table correctly, memory region must be
removed from request region. We had a series of patches to do this
culminating in:
	commit b4e008dc
	ACPI, APEI, EINJ, Refine the fix of resource conflict

but when ACPI5 support was added, we missed updating this area. So
when using EINJ table on an ACPI5 enabled machine, we get following error:

APEI: Can not request [mem 0x526b80000-0x526b80007] for APEI EINJ
Trigger registers

Fix this by checking for the acpi5 case and using the same code
that was added earlier.
Signed-off-by: default avatarChen Gong <gong.chen@linux.intel.com>
Signed-off-by: default avatarTony Luck <tony.luck@intel.com>
parent b69f0859
...@@ -367,7 +367,7 @@ static int __einj_error_trigger(u64 trigger_paddr, u32 type, ...@@ -367,7 +367,7 @@ static int __einj_error_trigger(u64 trigger_paddr, u32 type,
* This will cause resource conflict with regular memory. So * This will cause resource conflict with regular memory. So
* remove it from trigger table resources. * remove it from trigger table resources.
*/ */
if (param_extension && (type & 0x0038) && param2) { if ((param_extension || acpi5) && (type & 0x0038) && param2) {
struct apei_resources addr_resources; struct apei_resources addr_resources;
apei_resources_init(&addr_resources); apei_resources_init(&addr_resources);
trigger_param_region = einj_get_trigger_parameter_region( trigger_param_region = einj_get_trigger_parameter_region(
......
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment