[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <1430773335-22897-1-git-send-email-zjzhang@codeaurora.org>
Date: Mon, 4 May 2015 14:02:13 -0700
From: "Jonathan (Zhixiong) Zhang" <zjzhang@...eaurora.org>
To: Matt Fleming <matt.fleming@...el.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...hat.com>,
"H. Peter Anvin" <hpa@...or.com>, x86@...nel.org
Cc: "Jonathan (Zhixiong) Zhang" <zjzhang@...eaurora.org>,
linux-efi@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-acpi@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linaro-acpi@...ts.linaro.org
Subject: [PATCH 0/2] map GHES memory region with EFI memory map
From: "Jonathan (Zhixiong) Zhang" <zjzhang@...eaurora.org>
On a platform with APEI (ACPI Platform Error Interface) enabled, firmware
updates a memory region with hardware error record using nocache
attribute. When OS reads the region, since it maps the region with cache
attribute even though EFI memory map defines this region as uncached, OS
gets stale data and errorneously reports there is no new HW error.
When ghes driver maps the memory region, it uses the cache attribute
according to EFI memory map, if EFI memory map feature is enabled.
Since both arch/x86 and arc/ia64 implemented architecture agnostic EFI
memory map attribue lookup function, the code is moved from arch/x86
and arch/ia64 into EFI subsystem.
Jonathan (Zhixiong) Zhang (2):
efi: arch, x86: arch, ia64: rearrange EFI memmap related functions
acpi, apei: use EFI memmap to map GHES memory
arch/ia64/kernel/efi.c | 11 -----------
arch/x86/platform/efi/efi.c | 18 ------------------
drivers/acpi/apei/ghes.c | 13 +++++++++++++
drivers/firmware/efi/efi.c | 27 +++++++++++++++++++++++++++
include/linux/efi.h | 1 +
5 files changed, 41 insertions(+), 29 deletions(-)
--
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum,
a Linux Foundation Collaborative Project
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists