linux-acpi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: James Morse <james.morse@arm.com>
To: linux-acpi@vger.kernel.org
Cc: Lorenzo Pieralisi <lorenzo.pieralisi@arm.com>,
	Ard Biesheuvel <ard.biesheuvel@linaro.org>,
	Geoff Levand <geoff@infradead.org>,
	Riku Voipio <riku.voipio@linaro.org>,
	Mark Salter <msalter@redhat.com>,
	James Morse <james.morse@arm.com>,
	Hanjun Guo <hanjun.guo@linaro.org>,
	Sudeep Holla <sudeep.holla@arm.com>,
	linux-arm-kernel@lists.infradead.org
Subject: [RFC/RFT PATCH 1/2] efi: Add helper to retrieve runtime version number
Date: Thu, 28 Jun 2018 11:06:55 +0100	[thread overview]
Message-ID: <20180628100656.10692-2-james.morse@arm.com> (raw)
In-Reply-To: <20180628100656.10692-1-james.morse@arm.com>

Some RAS errors are related to an invalid hardware access that was
made by software. Sometimes this happens before the kernel runs.

For example, HPE's ProLiant m400 Server (aka moonshot) trips the
platforms RAS mechanism during ExitBootServices. Once the kernel
probes the RAS error descriptor regions, it finds a stale 'fatal
error', and hits the deck.

Quirking this platform based on the DMI data doesn't capture that
the bug lies in the platforms UEFI firmware. Expose the runtime
version, originally retrieved from the EFI system table's header
revision field, so that any future or unaffected platform firmware
isn't swept up too.

Signed-off-by: James Morse <james.morse@arm.com>
---
 include/linux/efi.h | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/include/linux/efi.h b/include/linux/efi.h
index 56add823f190..42ddf8399814 100644
--- a/include/linux/efi.h
+++ b/include/linux/efi.h
@@ -966,6 +966,11 @@ extern struct efi {
 	unsigned long flags;
 } efi;
 
+static inline unsigned int efi_get_runtime_version(void)
+{
+	return efi.runtime_version;
+}
+
 extern struct mm_struct efi_mm;
 
 static inline int
-- 
2.17.1

  reply	other threads:[~2018-06-28 10:06 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-28 10:06 [RFC/RFT PATCH 0/2] disable_hest quirk on HP m400 with bad UEFI firmwware James Morse
2018-06-28 10:06 ` James Morse [this message]
2018-06-28 10:06 ` [RFC/RFT PATCH 2/2] ACPI / APEI: Add DMI matching quirks for platforms that require hest_disable James Morse
2018-06-28 10:25 ` [RFC/RFT PATCH 0/2] disable_hest quirk on HP m400 with bad UEFI firmwware Ard Biesheuvel
2018-06-28 12:51   ` Lorenzo Pieralisi
2018-06-28 14:24   ` James Morse
2018-06-28 16:15   ` Geoff Levand
2018-06-28 20:56     ` Ard Biesheuvel
2018-07-03  8:46       ` Ian Campbell
2018-07-03  8:44   ` Ian Campbell
2018-07-03 15:17     ` Ard Biesheuvel
2018-07-03 15:47       ` Ian Campbell
2018-07-03 17:12         ` Lorenzo Pieralisi
2018-07-03 17:16           ` Ian Campbell
2018-07-03 17:39             ` Lorenzo Pieralisi
2018-07-03 19:47               ` Ian Campbell
2018-07-04  9:14                 ` Lorenzo Pieralisi
2018-07-04  9:47                 ` Ard Biesheuvel

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=20180628100656.10692-2-james.morse@arm.com \
    --to=james.morse@arm.com \
    --cc=ard.biesheuvel@linaro.org \
    --cc=geoff@infradead.org \
    --cc=hanjun.guo@linaro.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=lorenzo.pieralisi@arm.com \
    --cc=msalter@redhat.com \
    --cc=riku.voipio@linaro.org \
    --cc=sudeep.holla@arm.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;
as well as URLs for NNTP newsgroup(s).