From: "Luck, Tony" <tony.luck@intel.com>
To: "Alex G." <mr.nuke.me@gmail.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
Borislav Petkov <bp@alien8.de>,
alex_gagniuc@dellteam.com, austin_bolen@dell.com,
shyam_iyer@dell.com, "Rafael J. Wysocki" <rjw@rjwysocki.net>,
Len Brown <lenb@kernel.org>,
Tyler Baicar <tbaicar@codeaurora.org>,
Will Deacon <will.deacon@arm.com>,
James Morse <james.morse@arm.com>,
Shiju Jose <shiju.jose@huawei.com>,
"Jonathan (Zhixiong) Zhang" <zjzhang@codeaurora.org>,
Dongjiu Geng <gengdongjiu@huawei.com>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v6 1/2] acpi: apei: Rename ghes_severity() to ghes_cper_severity()
Date: Tue, 22 May 2018 11:45:33 -0700 [thread overview]
Message-ID: <20180522184532.GA4360@agluck-desk> (raw)
In-Reply-To: <5dc58180-d3c0-a9f0-282f-4be433c94052@gmail.com>
On Tue, May 22, 2018 at 01:19:34PM -0500, Alex G. wrote:
> Firmware started passing "fatal" GHES headers with the explicit intent of
> crashing an OS. At the same time, we've learnt how to handle these errors in
> a number of cases. With DPC (coming soon to firmware-first) the error is
> contained, and a non-issue.
Perhaps DPC is the change that you need to emphasize as to
why things are different now, so we can change the default
Linux behavior.
With the h/w guaranteeing that corrupt data is contained, we
should be safe to disregard BIOS indications of "fatal" problems
that could be anything and might show up in unknown ways some
time later if we keep running.
-Tony
next prev parent reply other threads:[~2018-05-22 18:45 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-21 13:49 [PATCH v6 0/2] acpi: apei: Improve PCIe error handling with FFS Alexandru Gagniuc
2018-05-21 13:49 ` [PATCH v6 1/2] acpi: apei: Rename ghes_severity() to ghes_cper_severity() Alexandru Gagniuc
2018-05-22 8:55 ` Rafael J. Wysocki
2018-05-22 13:38 ` Alex G.
2018-05-22 13:50 ` Borislav Petkov
2018-05-22 14:39 ` Alex G.
2018-05-22 14:54 ` Borislav Petkov
2018-05-22 15:22 ` Alex G.
2018-05-22 15:33 ` Borislav Petkov
2018-05-22 17:57 ` Luck, Tony
2018-05-22 18:10 ` Rafael J. Wysocki
2018-05-22 18:19 ` Alex G.
2018-05-22 18:45 ` Luck, Tony [this message]
2018-05-22 18:49 ` Alex G.
2018-05-22 18:33 ` Luck, Tony
2018-05-22 18:13 ` Alex G.
2018-05-22 18:13 ` Rafael J. Wysocki
2018-05-22 18:20 ` Alex G.
2018-05-22 21:20 ` Rafael J. Wysocki
2018-05-21 13:49 ` [PATCH v6 2/2] acpi: apei: Do not panic() on PCIe errors reported through GHES Alexandru Gagniuc
2018-05-21 14:27 ` Tyler Baicar
2018-05-21 17:40 ` Alex G.
2018-05-22 9:02 ` Rafael J. Wysocki
2018-05-22 14:32 ` Alex G.
2018-05-22 15:15 ` Tyler Baicar
2018-05-22 15:18 ` Alex G.
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=20180522184532.GA4360@agluck-desk \
--to=tony.luck@intel.com \
--cc=alex_gagniuc@dellteam.com \
--cc=austin_bolen@dell.com \
--cc=bp@alien8.de \
--cc=gengdongjiu@huawei.com \
--cc=james.morse@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mr.nuke.me@gmail.com \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=shiju.jose@huawei.com \
--cc=shyam_iyer@dell.com \
--cc=tbaicar@codeaurora.org \
--cc=will.deacon@arm.com \
--cc=zjzhang@codeaurora.org \
/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).