From: Cao jin <caoj.fnst@cn.fujitsu.com>
To: <linasvepstas@gmail.com>
Cc: "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>,
Jonathan Corbet <corbet@lwn.net>,
"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [PATCH] pci-error-recovery: doc cleanup
Date: Wed, 22 Mar 2017 14:55:27 +0800 [thread overview]
Message-ID: <58D21FDF.4000506@cn.fujitsu.com> (raw)
In-Reply-To: <CAHrUA34WX1sqEWJiuiy8yN2B1NHjDzj5UQ2A=0Nsdad1cVNjDw@mail.gmail.com>
CC MST who touched this file in last commit on it.
On 03/22/2017 01:48 PM, Linas Vepstas wrote:
> Hi,
>
> On Tue, Mar 21, 2017 at 9:24 PM, Cao jin <caoj.fnst@cn.fujitsu.com> wrote:
>> Include whitespace shooting; correction; typo fix; superfluous word
>> dropping.
>
>>
>> diff --git a/Documentation/PCI/pci-error-recovery.txt b/Documentation/PCI/pci-error-recovery.txt
>> index da3b217..0b6bb3e 100644
>> --- a/Documentation/PCI/pci-error-recovery.txt
>> +++ b/Documentation/PCI/pci-error-recovery.txt
>>
>> @@ -231,14 +231,14 @@ proceeds to STEP 4 (Slot Reset)
>> STEP 3: Link Reset
>> ------------------
>> The platform resets the link. This is a PCI-Express specific step
>> -and is done whenever a non-fatal error has been detected that can be
>> +and is done whenever a fatal error has been detected that can be
>> "solved" by resetting the link.
>
> First: I thought I saw a patch a few months ago that proposed removing
> the link rest step. I don't know if the patch was accepted or not.
>
Yes, I sent this one and I asked to ignore it. At that time, .link_reset
handler still exists, now is gone.
> If link resets are still supported, then they can only fix NON-fatal errors:
> basically, one resets the link, and only the link; one does NOT reset
> either the device driver, nor the device state. The idea is that after a link
> reset, communications with the device can immediately resume right
> where it left off. (this can be hard in practice, if the driver/firmware doesn't
> know what it was doing when the error occurred. this might be why no one
> implements it.) Anyway, the whole point of a link reset is that it is
> explicitly
> a non-fatal error.
>
Perhaps you are still talking about link re-training. After last commit
on this file, section "Link Reset" seems only focus on PCI-Express. If
it is a PCI-Express specific step, then I think the "fatal" &
"non-fatal" referred here are in the PCI-Express(AER) territory, and
according to the AER driver(function do_recovery()), platform level link
reset targeted to fatal error.
--
Sincerely,
Cao jin
next prev parent reply other threads:[~2017-03-22 6:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 13:24 Cao jin
2017-03-22 5:48 ` Linas Vepstas
2017-03-22 6:55 ` Cao jin [this message]
2017-03-29 21:51 ` Jonathan Corbet
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=58D21FDF.4000506@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 \
--cc=mst@redhat.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
Powered by JetHome