From: Wesley Sheng <wesley.sheng@amd.com>
To: Oliver O'Halloran <oohall@gmail.com>,
linasvepstas@gmail.com, ruscur@russell.cc, bhelgaas@google.com,
corbet@lwn.net, linux-pci@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: wesleyshenggit@sina.com, wesley.sheng@amd.com
Subject: Re: [PATCH] Documentation: PCI: pci-error-recovery: rearrange the general sequence
Date: Tue, 29 Jun 2021 11:34:37 +0800 [thread overview]
Message-ID: <20210629033437.GB1492@buildhost> (raw)
In-Reply-To: <CAOSf1CHaLCAsnB42Je+ynJ6xv-M8qmScbfOLSHVze7D4fEh66Q@mail.gmail.com>
On Fri, Jun 18, 2021 at 05:21:32PM +1000, Oliver O'Halloran wrote:
> On Fri, Jun 18, 2021 at 4:05 PM Wesley Sheng <wesley.sheng@amd.com> wrote:
> >
> > Reset_link() callback function was called before mmio_enabled() in
> > pcie_do_recovery() function actually, so rearrange the general
> > sequence betwen step 2 and step 3 accordingly.
>
> I don't think this is true in all cases. If pcie_do_recovery() is
> called with state==pci_channel_io_normal (i.e. non-fatal AER) the link
> won't be reset. EEH (ppc PCI error recovery thing) also uses
> .mmio_enabled() as described.
Yes, in case of non-fatal AER, reset_link() callback (aer_root_reset() for
AER and dpc_reset_link() for DPC) will not be invoked. And if
.error_detected() return PCI_ERS_RESULT_CAN_RECOVER, .mmio_enabled() be
called followed.
But if pcie_do_recovery() is called with state == pci_channel_io_frozen,
reset_link() callback is called after .error_detected() but before
.mmio_enabled(). So I thought Step 2: MMIO Enabled and Step 3: Link Reset
should rearrange their sequence.
WARNING: multiple messages have this Message-ID (diff)
From: Wesley Sheng <wesley.sheng@amd.com>
To: Oliver O'Halloran <oohall@gmail.com>,
linasvepstas@gmail.com, ruscur@russell.cc, bhelgaas@google.com,
corbet@lwn.net, linux-pci@vger.kernel.org,
linuxppc-dev@lists.ozlabs.org, linux-doc@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: wesley.sheng@amd.com, wesleyshenggit@sina.com
Subject: Re: [PATCH] Documentation: PCI: pci-error-recovery: rearrange the general sequence
Date: Tue, 29 Jun 2021 11:34:37 +0800 [thread overview]
Message-ID: <20210629033437.GB1492@buildhost> (raw)
In-Reply-To: <CAOSf1CHaLCAsnB42Je+ynJ6xv-M8qmScbfOLSHVze7D4fEh66Q@mail.gmail.com>
On Fri, Jun 18, 2021 at 05:21:32PM +1000, Oliver O'Halloran wrote:
> On Fri, Jun 18, 2021 at 4:05 PM Wesley Sheng <wesley.sheng@amd.com> wrote:
> >
> > Reset_link() callback function was called before mmio_enabled() in
> > pcie_do_recovery() function actually, so rearrange the general
> > sequence betwen step 2 and step 3 accordingly.
>
> I don't think this is true in all cases. If pcie_do_recovery() is
> called with state==pci_channel_io_normal (i.e. non-fatal AER) the link
> won't be reset. EEH (ppc PCI error recovery thing) also uses
> .mmio_enabled() as described.
Yes, in case of non-fatal AER, reset_link() callback (aer_root_reset() for
AER and dpc_reset_link() for DPC) will not be invoked. And if
.error_detected() return PCI_ERS_RESULT_CAN_RECOVER, .mmio_enabled() be
called followed.
But if pcie_do_recovery() is called with state == pci_channel_io_frozen,
reset_link() callback is called after .error_detected() but before
.mmio_enabled(). So I thought Step 2: MMIO Enabled and Step 3: Link Reset
should rearrange their sequence.
next prev parent reply other threads:[~2021-06-29 3:34 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-18 6:04 [PATCH] Documentation: PCI: pci-error-recovery: rearrange the general sequence Wesley Sheng
2021-06-18 6:04 ` Wesley Sheng
2021-06-18 7:21 ` Oliver O'Halloran
2021-06-18 7:21 ` Oliver O'Halloran
2021-06-29 3:34 ` Wesley Sheng [this message]
2021-06-29 3:34 ` Wesley Sheng
2021-07-01 22:22 ` Bjorn Helgaas
2021-07-01 22:22 ` Bjorn Helgaas
2021-07-02 2:41 ` Wesley Sheng
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=20210629033437.GB1492@buildhost \
--to=wesley.sheng@amd.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=linuxppc-dev@lists.ozlabs.org \
--cc=oohall@gmail.com \
--cc=ruscur@russell.cc \
--cc=wesleyshenggit@sina.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.