From: Randy Dunlap <rdunlap@infradead.org>
To: Oza Pawandeep <poza@codeaurora.org>,
Bjorn Helgaas <bhelgaas@google.com>,
Philippe Ombredanne <pombredanne@nexb.com>,
Thomas Gleixner <tglx@linutronix.de>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kate Stewart <kstewart@linuxfoundation.org>,
linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Dongdong Liu <liudongdong3@huawei.com>,
Keith Busch <keith.busch@intel.com>, Wei Zhang <wzhang@fb.com>,
Sinan Kaya <okaya@codeaurora.org>,
Timur Tabi <timur@codeaurora.org>
Subject: Re: [PATCH v9 7/7] PCI/DPC: Enumerate the devices after DPC trigger event
Date: Thu, 22 Feb 2018 11:23:28 -0800 [thread overview]
Message-ID: <d8da89bf-aaa1-c6ed-d21a-4cd51265d4a2@infradead.org> (raw)
In-Reply-To: <1519285571-5634-8-git-send-email-poza@codeaurora.org>
On 02/21/2018 11:46 PM, Oza Pawandeep wrote:
> Implement error_resume callback in DPC so, after DPC trigger event
> enumerates the devices beneath.
>
> Signed-off-by: Oza Pawandeep <poza@codeaurora.org>
>
> diff --git a/drivers/pci/pcie/pcie-dpc.c b/drivers/pci/pcie/pcie-dpc.c
> index fce4518..59c01c7 100644
> --- a/drivers/pci/pcie/pcie-dpc.c
> +++ b/drivers/pci/pcie/pcie-dpc.c
> @@ -129,6 +129,23 @@ static void dpc_wait_link_inactive(struct dpc_dev *dpc)
> }
>
> /**
> + * dpc_error_resume - enumerate the devices beneath
> + * @dev: pointer to Root Port's pci_dev data structure
* @pdev: ...
> + *
> + * Invoked by Port Bus driver during nonfatal recovery.
> + */
> +static void dpc_error_resume(struct pci_dev *pdev)
> +{
> + bool active = true;
> +
> + if (pci_wait_for_link(pdev, active)) {
> + pci_lock_rescan_remove();
> + pci_rescan_bus(pdev->bus);
> + pci_unlock_rescan_remove();
> + }
> +}
> +
> +/**
> * dpc_reset_link - reset link DPC routine
> * @dev: pointer to Root Port's pci_dev data structure
> *
> diff --git a/drivers/pci/pcie/pcie-err.c b/drivers/pci/pcie/pcie-err.c
> index 6844347..4950f49 100644
> --- a/drivers/pci/pcie/pcie-err.c
> +++ b/drivers/pci/pcie/pcie-err.c
> @@ -256,6 +258,15 @@ static pci_ers_result_t broadcast_error_message(struct pci_dev *dev,
> result_data.result = PCI_ERS_RESULT_RECOVERED;
>
> if (dev->hdr_type == PCI_HEADER_TYPE_BRIDGE) {
> + /* If DPC is triggered, call resume error hanlder
handler
Kernel multi-line comment style is:
/*
* Begin comment here.
* foo bar blah
*/
> + * because, at this point we can safely assume that
> + * link recovery has happened.
> + */
> + if ((severity == DPC_FATAL) &&
> + (cb == report_resume)) {
> + cb(dev, NULL);
> + return PCI_ERS_RESULT_RECOVERED;
> + }
> /*
> * If the error is reported by a bridge, we think this error
> * is related to the downstream link of the bridge, so we
thanks,
--
~Randy
next prev parent reply other threads:[~2018-02-22 19:23 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 7:46 [PATCH v9 0/7] Address error and recovery for AER and DPC Oza Pawandeep
2018-02-22 7:46 ` [PATCH v9 1/7] PCI/AER: Rename error recovery to generic pci naming Oza Pawandeep
2018-02-22 7:46 ` [PATCH v9 2/7] PCI/AER: factor out error reporting from AER Oza Pawandeep
2018-02-22 19:23 ` Randy Dunlap
2018-02-23 6:31 ` poza
2018-02-23 6:36 ` poza
2018-02-22 7:46 ` [PATCH v9 3/7] PCI/ERR: add mutex to synchronize recovery Oza Pawandeep
2018-02-22 7:46 ` [PATCH v9 4/7] PCI/DPC: Unify and plumb error handling into DPC Oza Pawandeep
2018-02-22 19:23 ` Randy Dunlap
2018-02-23 5:20 ` poza
2018-02-22 7:46 ` [PATCH v9 5/7] PCI/AER: Unify aer error defines at single space Oza Pawandeep
2018-02-22 7:46 ` [PATCH v9 6/7] PCI: Unify wait for link active into generic pci Oza Pawandeep
2018-02-22 7:46 ` [PATCH v9 7/7] PCI/DPC: Enumerate the devices after DPC trigger event Oza Pawandeep
2018-02-22 19:23 ` Randy Dunlap [this message]
2018-02-23 5:22 ` poza
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=d8da89bf-aaa1-c6ed-d21a-4cd51265d4a2@infradead.org \
--to=rdunlap@infradead.org \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=keith.busch@intel.com \
--cc=kstewart@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=liudongdong3@huawei.com \
--cc=okaya@codeaurora.org \
--cc=pombredanne@nexb.com \
--cc=poza@codeaurora.org \
--cc=tglx@linutronix.de \
--cc=timur@codeaurora.org \
--cc=wzhang@fb.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
all inboxes | Powered by JetHome®