From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: Jonathan Corbet <corbet@lwn.net>
Cc: <linasvepstas@gmail.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
<linux-doc@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: [PATCH] pci-error-recover: doc cleanup
Date: Mon, 19 Dec 2016 11:25:51 +0800 [thread overview]
Message-ID: <5857533F.1030904@cn.fujitsu.com> (raw)
In-Reply-To: <20161209073713.43ed92ea@lwn.net>
Sorry for late.
On 12/09/2016 10:37 PM, Jonathan Corbet wrote:
> On Fri, 9 Dec 2016 14:37:47 +0800
> Cao jin <caoj.fnst@cn.fujitsu.com> wrote:
>
>> I am little confused too, even not sure if we are talking the same
>> *fatal error*, I am talking the fatal error defined in PCI Express spec,
>> chapter 6.2.2.2.1:
>
> Therein lies my original discomfort with the change; it didn't seem to
> make sense to talk about recovering from a fatal error. Perhaps making
> it "is done whenever a fatal error (as defined in section 6.2.2.2.1) has
> been detected that can be "solved" by resetting the link" or something
> like that to make it clear how the term is being used?
>
I find that the .link_reset callback of struct pci_error_handlers isn't
called by anyone(if I didn't miss anything), and just a few drivers
implement this callback, and their implementation seems meaningless.
And the reset_link() provided by aer driver seems is a different thing
with .link_reset callback. So I am guessing this patch probably is not
quite suitable, and the doc maybe need update totally.
--
Sincerely,
Cao jin
next prev parent reply other threads:[~2016-12-19 3:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-08 8:16 [PATCH] pci-error-recover: doc cleanup Cao jin
2016-12-08 14:05 ` Jonathan Corbet
2016-12-08 14:13 ` Cao jin
2016-12-09 6:24 ` Linas Vepstas
2016-12-09 6:37 ` Cao jin
2016-12-09 6:44 ` Linas Vepstas
2016-12-09 7:59 ` Cao jin
2016-12-09 16:11 ` Alex Williamson
2016-12-09 14:37 ` Jonathan Corbet
2016-12-19 3:25 ` Cao jin [this message]
2016-12-09 6:50 ` Andrew Donnellan
2016-12-14 2:39 ` Gavin Shan
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=5857533F.1030904@cn.fujitsu.com \
--to=caoj.fnst@cn.fujitsu.com \
--cc=bhelgaas@google.com \
--cc=corbet@lwn.net \
--cc=linasvepstas@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
/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