From: 陈卓 <chenzhuo.1@bytedance.com>
To: Sathyanarayanan Kuppuswamy
<sathyanarayanan.kuppuswamy@linux.intel.com>,
ruscur@russell.cc, oohall@gmail.com, bhelgaas@google.com
Cc: lukas@wunner.de, jan.kiszka@siemens.com,
stuart.w.hayes@gmail.com, linuxppc-dev@lists.ozlabs.org,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] PCI/ERR: Use pcie_aer_is_native() to judge whether OS owns AER
Date: Wed, 27 Jul 2022 13:35:56 +0800 [thread overview]
Message-ID: <cfd44d9c-453b-e498-2630-9057947cf3cd@bytedance.com> (raw)
In-Reply-To: <b5c746db-f6a0-d89e-6db5-e4a206c9237a@linux.intel.com>
On 7/26/22 9:02 PM, Sathyanarayanan Kuppuswamy wrote:
>
>
> On 7/26/22 8:53 PM, Zhuo Chen wrote:
>> Use pcie_aer_is_native() in place of "host->native_aer ||
>> pcie_ports_native" to judge whether OS has native control of AER
>> in pcie_do_recovery().
>>
>> Replace "dev->aer_cap && (pcie_ports_native || host->native_aer)" in
>> get_port_device_capability() with pcie_aer_is_native(), which has no
>> functional changes.
>>
>> Signed-off-by: Zhuo Chen <chenzhuo.1@bytedance.com>
>> ---
>
> Patch looks better now. It looks like following two changes
> can also be replaced with pcie_aer_is_native() check.
>
> drivers/pci/pcie/aer.c:1407: if ((host->native_aer || pcie_ports_native) && aer) {
> drivers/pci/pcie/aer.c:1426: if ((host->native_aer || pcie_ports_native) && aer) {
Good advice. But I wonder is there a scenario that dev->rcec ("root") is
NULL meanwhile dev->aer_cap is not NULL? If so, replace
"(host->native_aer || pcie_ports_native) && aer" with
pcie_aer_is_native() will change original function.
>
>
>
>> Changelog:
>> v3:
>> - Simplify why we use pcie_aer_is_native().
>> - Revert modification of pci_aer_clear_nonfatal_status() and comments.
>> v2:
>> - Add details and note in commit log.
>> ---
>> drivers/pci/pcie/err.c | 3 +--
>> drivers/pci/pcie/portdrv_core.c | 3 +--
>> 2 files changed, 2 insertions(+), 4 deletions(-)
>>
>> diff --git a/drivers/pci/pcie/err.c b/drivers/pci/pcie/err.c
>> index 0c5a143025af..121a53338e44 100644
>> --- a/drivers/pci/pcie/err.c
>> +++ b/drivers/pci/pcie/err.c
>> @@ -184,7 +184,6 @@ pci_ers_result_t pcie_do_recovery(struct pci_dev *dev,
>> int type = pci_pcie_type(dev);
>> struct pci_dev *bridge;
>> pci_ers_result_t status = PCI_ERS_RESULT_CAN_RECOVER;
>> - struct pci_host_bridge *host = pci_find_host_bridge(dev->bus);
>>
>> /*
>> * If the error was detected by a Root Port, Downstream Port, RCEC,
>> @@ -243,7 +242,7 @@ pci_ers_result_t pcie_do_recovery(struct pci_dev *dev,
>> * it is responsible for clearing this status. In that case, the
>> * signaling device may not even be visible to the OS.
>> */
>> - if (host->native_aer || pcie_ports_native) {
>> + if (pcie_aer_is_native(dev)) {
>> pcie_clear_device_status(dev);
>> pci_aer_clear_nonfatal_status(dev);
>> }
>> diff --git a/drivers/pci/pcie/portdrv_core.c b/drivers/pci/pcie/portdrv_core.c
>> index 604feeb84ee4..98c18f4a01b2 100644
>> --- a/drivers/pci/pcie/portdrv_core.c
>> +++ b/drivers/pci/pcie/portdrv_core.c
>> @@ -221,8 +221,7 @@ static int get_port_device_capability(struct pci_dev *dev)
>> }
>>
>> #ifdef CONFIG_PCIEAER
>> - if (dev->aer_cap && pci_aer_available() &&
>> - (pcie_ports_native || host->native_aer)) {
>> + if (pcie_aer_is_native(dev) && pci_aer_available()) {
>> services |= PCIE_PORT_SERVICE_AER;
>>
>> /*
>
Thanks,
Zhuo Chen
next prev parent reply other threads:[~2022-07-27 5:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-27 3:53 [PATCH v3] PCI/ERR: Use pcie_aer_is_native() to judge whether OS owns AER Zhuo Chen
2022-07-27 4:02 ` Sathyanarayanan Kuppuswamy
2022-07-27 5:35 ` 陈卓 [this message]
2022-07-27 9:37 ` Zhuo Chen
2022-08-02 22:18 ` Sathyanarayanan Kuppuswamy
2022-08-12 9:27 ` [External] " Zhuo Chen
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=cfd44d9c-453b-e498-2630-9057947cf3cd@bytedance.com \
--to=chenzhuo.1@bytedance.com \
--cc=bhelgaas@google.com \
--cc=jan.kiszka@siemens.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=lukas@wunner.de \
--cc=oohall@gmail.com \
--cc=ruscur@russell.cc \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=stuart.w.hayes@gmail.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