[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20200722110146.GW3703480@smile.fi.intel.com>
Date: Wed, 22 Jul 2020 14:01:46 +0300
From: Andy Shevchenko <andriy.shevchenko@...ux.intel.com>
To: Shiju Jose <shiju.jose@...wei.com>
Cc: linux-acpi@...r.kernel.org, linux-pci@...r.kernel.org,
linux-kernel@...r.kernel.org, rjw@...ysocki.net,
helgaas@...nel.org, bp@...en8.de, james.morse@....com,
lenb@...nel.org, tony.luck@...el.com, dan.carpenter@...cle.com,
zhangliguang@...ux.alibaba.com, wangkefeng.wang@...wei.com,
jroedel@...e.de, linuxarm@...wei.com, yangyicong@...ilicon.com,
jonathan.cameron@...wei.com, tanxiaofei@...wei.com
Subject: Re: [PATCH v13 1/2] ACPI / APEI: Add a notifier chain for unknown
(vendor) CPER records
On Wed, Jul 22, 2020 at 11:39:51AM +0100, Shiju Jose wrote:
> CPER records describing a firmware-first error are identified by GUID.
> The ghes driver currently logs, but ignores any unknown CPER records.
> This prevents describing errors that can't be represented by a standard
> entry, that would otherwise allow a driver to recover from an error.
> The UEFI spec calls these 'Non-standard Section Body' (N.2.3 of
> version 2.8).
>
> Add a notifier chain for these non-standard/vendor-records. Callers
> must identify their type of records by GUID.
>
> Record data is copied to memory from the ghes_estatus_pool to allow
> us to keep it until after the notifier has run.
>
> Co-developed-by: James Morse <james.morse@....com>
Co-developed-by: is going _in conjunction with_ SoB tag which is missing here.
> Signed-off-by: Shiju Jose <shiju.jose@...wei.com>
--
With Best Regards,
Andy Shevchenko
Powered by blists - more mailing lists