From: Shuai Xue <xueshuai@linux.alibaba.com>
To: Sathyanarayanan Kuppuswamy
<sathyanarayanan.kuppuswamy@linux.intel.com>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, bhelgaas@google.com,
kbusch@kernel.org
Cc: mahesh@linux.ibm.com, oohall@gmail.com,
Jonathan.Cameron@huawei.com, terry.bowman@amd.com
Subject: Re: [PATCH v3 3/4] PCI/DPC: Run recovery on device that detected the error
Date: Wed, 12 Feb 2025 13:51:41 +0800 [thread overview]
Message-ID: <a89b973e-a168-49f1-8a82-2e9280cc08b6@linux.alibaba.com> (raw)
In-Reply-To: <c1837324-98b0-4548-893f-b14e89ced9db@linux.intel.com>
在 2025/2/12 05:23, Sathyanarayanan Kuppuswamy 写道:
>
> On 2/7/25 1:34 AM, Shuai Xue wrote:
>> The current implementation of pcie_do_recovery() assumes that the
>> recovery process is executed on the device that detected the error.
>> However, the DPC driver currently passes the error port that experienced
>> the DPC event to pcie_do_recovery().
>>
>> Use the SOURCE ID register to correctly identify the device that detected the
>> error. By passing this error device to pcie_do_recovery(), subsequent
>> patches will be able to accurately access AER status of the error device.
>
> I also recommend adding info about the fact that pcie_do_recovery() finds
> upstream bridge to run the recovery process and hence should not observe
> any functional changes (compared to previous version)
Got it. Will add it.
>
>>
>> Signed-off-by: Shuai Xue <xueshuai@linux.alibaba.com>
>> ---
>> drivers/pci/pci.h | 2 +-
>> drivers/pci/pcie/dpc.c | 25 +++++++++++++++++++++----
>> drivers/pci/pcie/edr.c | 7 ++++---
>> 3 files changed, 26 insertions(+), 8 deletions(-)
>>
>> diff --git a/drivers/pci/pci.h b/drivers/pci/pci.h
>> index 01e51db8d285..870d2fbd6ff2 100644
>> --- a/drivers/pci/pci.h
>> +++ b/drivers/pci/pci.h
>> @@ -572,7 +572,7 @@ struct rcec_ea {
>> void pci_save_dpc_state(struct pci_dev *dev);
>> void pci_restore_dpc_state(struct pci_dev *dev);
>> void pci_dpc_init(struct pci_dev *pdev);
>> -void dpc_process_error(struct pci_dev *pdev);
>> +struct pci_dev *dpc_process_error(struct pci_dev *pdev);
>> pci_ers_result_t dpc_reset_link(struct pci_dev *pdev);
>> bool pci_dpc_recovered(struct pci_dev *pdev);
>> unsigned int dpc_tlp_log_len(struct pci_dev *dev);
>> diff --git a/drivers/pci/pcie/dpc.c b/drivers/pci/pcie/dpc.c
>> index 1a54a0b657ae..a91440f3b118 100644
>> --- a/drivers/pci/pcie/dpc.c
>> +++ b/drivers/pci/pcie/dpc.c
>> @@ -253,10 +253,17 @@ static int dpc_get_aer_uncorrect_severity(struct pci_dev *dev,
>> return 1;
>> }
>> -void dpc_process_error(struct pci_dev *pdev)
>> +/**
>> + * dpc_process_error - handle the DPC error status
>> + * @pdev: the port that experienced the containment event
>> + *
>> + * Return the device that detected the error.
>> + */
>
> Add a note about calling pci_dev_put() after using this function.
Will add it in next version.
Thanks.
Shuai
next prev parent reply other threads:[~2025-02-12 5:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-07 9:34 [PATCH v3 0/4] PCI/AER: Report fatal errors of RCiEP and EP if link recoverd Shuai Xue
2025-02-07 9:34 ` [PATCH v3 1/4] PCI/DPC: Rename pdev to err_port for dpc_handler Shuai Xue
2025-02-11 21:17 ` Sathyanarayanan Kuppuswamy
2025-02-12 2:47 ` Shuai Xue
2025-02-07 9:34 ` [PATCH v3 2/4] PCI/EDR: Rename edev to err_port for edr_handle_event Shuai Xue
2025-02-07 9:34 ` [PATCH v3 3/4] PCI/DPC: Run recovery on device that detected the error Shuai Xue
2025-02-11 21:23 ` Sathyanarayanan Kuppuswamy
2025-02-12 5:51 ` Shuai Xue [this message]
2025-02-07 9:35 ` [PATCH v3 4/4] PCI/AER: Report fatal errors of RCiEP and EP if link recoverd Shuai Xue
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=a89b973e-a168-49f1-8a82-2e9280cc08b6@linux.alibaba.com \
--to=xueshuai@linux.alibaba.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=bhelgaas@google.com \
--cc=kbusch@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=mahesh@linux.ibm.com \
--cc=oohall@gmail.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=terry.bowman@amd.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