[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e92c6c4f33c84f23ae47137f4ecb11f0@ausx13mps321.AMER.DELL.COM>
Date: Tue, 20 Nov 2018 22:36:26 +0000
From: <Alex_Gagniuc@...lteam.com>
To: <okaya@...nel.org>, <mr.nuke.me@...il.com>, <keith.busch@...el.com>
Cc: <baicar.tyler@...il.com>, <Austin.Bolen@...l.com>,
<Shyam.Iyer@...l.com>, <lukas@...ner.de>, <bhelgaas@...gle.com>,
<rjw@...ysocki.net>, <lenb@...nel.org>, <ruscur@...sell.cc>,
<sbobroff@...ux.ibm.com>, <oohall@...il.com>,
<linux-pci@...r.kernel.org>, <linux-acpi@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <linuxppc-dev@...ts.ozlabs.org>
Subject: Re: [PATCH 0/2] PCI/AER: Consistently use _OSC to determine who owns
AER
On 11/20/2018 04:08 PM, Sinan Kaya wrote:
> One version is:
> "if HEST table is present, ignore _OSC"
> or
> Another version is:
> "if HEST table is present, make sure that FW sets _OSC bit for AER to
> false. Otherwise, warn like crazy that this BIOS is broken and needs
> an update and can cause all sorts of trouble"
ACPI 6.2 Ch 6.2.11.3, Table 6-197
PCI Express Advanced Error Reporting control
The firmware sets this bit to 1 to grant control over PCI
Express Advanced Error Reporting.
If firmware allows the OS control of this feature, then in the
context of the _OSC method it must ensure that error messages
are routed to device interrupts as described in the PCI
Express Base Specification. Additionally, after control is
transferred to the OS, firmware must not modify the Advanced
Error Reporting Capability. If control of this feature was
requested and denied or was not requested, firmware returns
this bit set to 0.
Powered by blists - more mailing lists