From: Aili Yao <yaoaili@kingsoft.com>
To: James Morse <james.morse@arm.com>
Cc: <rjw@rjwysocki.net>, <lenb@kernel.org>, <tony.luck@intel.com>,
<bp@alien8.de>, <linux-acpi@vger.kernel.org>,
<linux-edac@vger.kernel.org>, <yangfeng1@kingsoft.com>,
<CHENGUOMIN@kingsoft.com>, <yaoaili@kingsoft.com>
Subject: Re: [PATCH] Dump cper error table in mce_panic
Date: Wed, 18 Nov 2020 11:12:14 +0800 [thread overview]
Message-ID: <20201118111140.0c330108@aili-OptiPlex-7020> (raw)
In-Reply-To: <112d8a04-4f0d-6705-4da1-e8d95a14dbaf@arm.com>
Hi, Thanks for your comments!
On Fri, 6 Nov 2020 19:35:32 +0000
James Morse <james.morse@arm.com> wrote:
> You appear to have something that behaves as GHES-ASSIST. Can you post the decompiled dump
> of your HEST table? (decompiled, no binaries!) If its large, you can post it to me off
> list and I'll copy the relevant bits here...
>
I think we we can reach a consensus, from and follow Intel Document #563361 23.1 :
Feature Name MCA 2.0 Recovery (as per EMCA Gen2 architecture)
Feature Description
Software layer assisted recovery from uncorrected data errors as defined by the EMCA Gen2
specification. EMCA Gen2 is a capability that allows firmware to intercept errors triggered via Machine
Check Architecture (corrected and uncorrected errors) enabling a Firmware First Model (FFM) of error
handling and possible recovery.
Use Case
Enhanced error reporting to support Firmware First Model (FFM) with following attributes:
1. Allows the SMM code to intercept the MCE/CMCI.
2. Allows the SMM code to write the MCA Status/Add/Misc registers.
3. Allows the SMM code to generate MCEs.
4. Allows the DSM based pointer for enhanced error logs.
5. Additional IA32_MCG_CAP bit for eMCA support
>
> If and only if those GHES are marked as GHES_ASSIST.
>
> If they are not, then you have a fully fledged firwmare-first system.
>
Yeah, This should be GHES_ASSIST, But For x86, BIOS don't supply a hest table for it as BIOS will trigger
MCE, It's out of APEI scope.
--
Best Regards!
Aili Yao
next prev parent reply other threads:[~2020-11-18 3:12 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-04 6:50 [PATCH] Dump cper error table in mce_panic yaoaili126
2020-11-04 10:16 ` kernel test robot
2020-11-06 19:35 ` James Morse
2020-11-18 3:12 ` Aili Yao [this message]
2020-11-17 9:58 ` [PATCH v2] " Aili Yao
2020-11-18 12:45 ` Borislav Petkov
2020-11-19 5:40 ` Aili Yao
2020-11-19 17:45 ` Borislav Petkov
2020-11-20 3:40 ` Aili Yao
2020-11-20 9:22 ` Aili Yao
2020-11-20 10:24 ` Borislav Petkov
2021-01-28 12:01 ` Aili Yao
2021-01-28 17:22 ` Luck, Tony
2021-02-23 9:18 ` Aili Yao
2021-02-23 19:32 ` Luck, Tony
2021-02-24 9:56 ` Aili Yao
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=20201118111140.0c330108@aili-OptiPlex-7020 \
--to=yaoaili@kingsoft.com \
--cc=CHENGUOMIN@kingsoft.com \
--cc=bp@alien8.de \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-edac@vger.kernel.org \
--cc=rjw@rjwysocki.net \
--cc=tony.luck@intel.com \
--cc=yangfeng1@kingsoft.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