mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Chen Gong <gong.chen@linux.intel.com>,
	LKML <linux-kernel@vger.kernel.org>,
	linux-pci@vger.kernel.org, Huang Ying <ying.huang@intel.com>,
	Hidetoshi Seto <seto.hidetoshi@jp.fujitsu.com>,
	Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>,
	Matthew Garrett <mjg59@srcf.ucam.org>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [PATCH] PCI / PCIe / AER: Disable native AER service if BIOS has precedence (v2) (was: Re: [PATCH]  PCI / PCIe / AER ...)
Date: Fri, 24 Sep 2010 09:53:55 -0700	[thread overview]
Message-ID: <20100924095355.36a7b064@jbarnes-desktop> (raw)
In-Reply-To: <201009201850.00626.rjw@sisk.pl>

On Mon, 20 Sep 2010 18:50:00 +0200
"Rafael J. Wysocki" <rjw@sisk.pl> wrote:

> On Monday, September 20, 2010, Chen Gong wrote:
> > 于 9/20/2010 6:02 AM, Rafael J. Wysocki 写道:
> > > From: Rafael J. Wysocki<rjw@sisk.pl>
> > >
> > > There is a design issue related to PCIe AER and _OSC that the BIOS
> > > may be asked to grant control of the AER service even if some
> > > Hardware Error Source Table (HEST) entries contain information
> > > meaning that the BIOS really should control it.  Namely,
> > > pcie_port_acpi_setup() calls pcie_aer_get_firmware_first() that
> > > determines whether or not the AER service should be controlled by
> > > the BIOS on the basis of the HEST information for the given PCIe
> > > port.  The BIOS is asked to grant control of the AER service for
> > > a PCIe Root Complex if pcie_aer_get_firmware_first() returns 'false'
> > > for at least one root port in that complex, even if all of the other
> > > root ports' HEST entries have the FIRMWARE_FIRST flag set (and none
> > > of them has the GLOBAL flag set).  However, if the AER service is
> > > controlled by the kernel, that may interfere with the BIOS' handling
> > > of the error sources having the FIRMWARE_FIRST flag.  Moreover,
> > > there may be PCIe endpoints that have the FIRMWARE_FIRST flag set in
> > > HEST and are attached to the root ports in question, in which case it
> > > also may be unsafe to ask the BIOS for control of the AER service.
> > >
> > > For this reason, introduce a function checking if there's at least
> > > one PCIe-related HEST entry with the FIRMWARE_FIRST flag set and
> > > disable the native AER service altogether if this function returns
> > > 'true'.

Applied the second patch to my linux-next branch, thanks.

-- 
Jesse Barnes, Intel Open Source Technology Center

  reply	other threads:[~2010-09-24 16:54 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-09-19 22:02 [PATCH] PCI / PCIe / AER: Disable native AER service if BIOS has precedence Rafael J. Wysocki
2010-09-20  6:18 ` Chen Gong
2010-09-20 16:50   ` [PATCH] PCI / PCIe / AER: Disable native AER service if BIOS has precedence (v2) (was: Re: [PATCH] PCI / PCIe / AER ...) Rafael J. Wysocki
2010-09-24 16:53     ` Jesse Barnes [this message]
2010-09-25  5:51     ` Huang Ying
2010-09-25 20:37       ` Rafael J. Wysocki

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=20100924095355.36a7b064@jbarnes-desktop \
    --to=jbarnes@virtuousgeek.org \
    --cc=gong.chen@linux.intel.com \
    --cc=kaneshige.kenji@jp.fujitsu.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pci@vger.kernel.org \
    --cc=mjg59@srcf.ucam.org \
    --cc=rjw@sisk.pl \
    --cc=seto.hidetoshi@jp.fujitsu.com \
    --cc=ying.huang@intel.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

Powered by JetHome