From: Keith Busch <kbusch@kernel.org>
To: Yicong Yang <yangyicong@hisilicon.com>
Cc: linux-pci@vger.kernel.org, helgaas@kernel.org, keith.busch@intel.com
Subject: Re: [Query]: PCIe Root Port Error Recovery
Date: Tue, 12 Nov 2019 00:26:50 +0900 [thread overview]
Message-ID: <20191111152650.GA10851@redsun51.ssa.fujisawa.hgst.com> (raw)
In-Reply-To: <255b77ba-13bd-c7f1-c7ab-d0e6bd398f2c@hisilicon.com>
On Mon, Nov 11, 2019 at 11:31:59AM +0800, Yicong Yang wrote:
> hello,
>
> I found that the root port itself is not handled in pcie_do_recovery() function
> and I noticed the commit(bfcb79f) in reset_link(), err.c writes:
> "If a Downstream Port (including a Root Port) reports an error, we assume the Port itself is reliable and we need to
> reset its downstream link"
>
> Is it real that the root port is always reliable and
> How to recover the root ports if it do meet some errors?
It's only that the path to the port is considered accessible, nothing
more. The port managed to send a notification that the CPU received,
so we assume communication goes both ways.
prev parent reply other threads:[~2019-11-11 15:27 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-11 3:31 [Query]: PCIe Root Port Error Recovery Yicong Yang
2019-11-11 15:26 ` Keith Busch [this message]
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=20191111152650.GA10851@redsun51.ssa.fujisawa.hgst.com \
--to=kbusch@kernel.org \
--cc=helgaas@kernel.org \
--cc=keith.busch@intel.com \
--cc=linux-pci@vger.kernel.org \
--cc=yangyicong@hisilicon.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;
as well as URLs for NNTP newsgroup(s).