From: Matt Domsch <Matt_Domsch@dell.com>
To: Kenji Kaneshige <kaneshige.kenji@jp.fujitsu.com>
Cc: linux-pci@vger.kernel.org, linux-acpi@vger.kernel.org,
Tom Long Nguyen <tom.l.nguyen@intel.com>,
Zhang Yanmin <yanmin.zhang@intel.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] PCIe AER: honor ACPI HEST FIRMWARE FIRST mode
Date: Fri, 9 Oct 2009 13:28:11 -0500 [thread overview]
Message-ID: <20091009182810.GB24889@mock.linuxdev.us.dell.com> (raw)
In-Reply-To: <4ACEE220.1020705@jp.fujitsu.com>
On Fri, Oct 09, 2009 at 04:11:28PM +0900, Kenji Kaneshige wrote:
> In the current AER driver implementation, correctable, non-fatal,
> fatal, unsupported request reporting enable bits in PCIe device
> control register can be changed by adapter card drivers through pci_enable_pcie_error_reporting() or pci_disable_pcie_error_reporting()
> APIs, regardless of _OSC evaluation result.
>
> I'm not sure, but I guess you might need to prevent those bits
> from being changed in the Firmware First mode.
You are correct. Thank you for the catch. I don't know if we can
prevent changing these bits via the raw operations, but we can prevent
them in these functions. Patch to follow does so.
--
Matt Domsch
Technology Strategist, Dell Office of the CTO
linux.dell.com & www.dell.com/linux
next prev parent reply other threads:[~2009-10-09 18:28 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-06 17:33 [PATCH] PCIe AER: honor ACPI HEST FIRMWARE FIRST mode Matt Domsch
2009-10-08 0:59 ` Hidetoshi Seto
[not found] ` <851fc09e0910082221q7f832c22xfc0d01ab72a97c3f@mail.gmail.com>
2009-10-09 5:55 ` Fwd: " Huang Ying
2009-10-09 14:31 ` Matt Domsch
2009-10-09 7:11 ` Kenji Kaneshige
2009-10-09 18:28 ` Matt Domsch [this message]
2009-10-09 18:33 ` Matt Domsch
2009-10-29 14:15 ` Matt Domsch
2009-10-29 16:48 ` Jesse Barnes
2009-10-30 2:16 ` Hidetoshi Seto
2009-10-30 2:53 ` Matt Domsch
2009-10-30 3:24 ` Hidetoshi Seto
2009-11-02 17:51 ` Matt Domsch
2009-11-04 17:11 ` Jesse Barnes
2009-11-04 20:55 ` Yinghai Lu
2009-11-04 20:55 ` Yinghai Lu
2009-11-04 21:05 ` Jesse Barnes
2009-11-04 21:07 ` Jesse Barnes
2009-11-04 21:07 ` Jesse Barnes
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=20091009182810.GB24889@mock.linuxdev.us.dell.com \
--to=matt_domsch@dell.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=tom.l.nguyen@intel.com \
--cc=yanmin.zhang@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.