From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Sinan Kaya <okaya@codeaurora.org>, Bjorn Helgaas <helgaas@kernel.org>
Cc: linux-pci@vger.kernel.org, Bjorn Helgaas <bhelgaas@google.com>,
Michael Neuling <michael.neuling@au1.ibm.com>,
linux-pci-owner@vger.kernel.org
Subject: Re: PCIe resets/restore and lack of CRS wait
Date: Fri, 23 Mar 2018 09:02:44 +1100 [thread overview]
Message-ID: <1521756164.16434.319.camel@kernel.crashing.org> (raw)
In-Reply-To: <6aec45f1-74d9-d36f-7169-0c91733985e3@codeaurora.org>
On Thu, 2018-03-22 at 12:54 -0500, Sinan Kaya wrote:
> Ben,
>
> On 3/22/2018 9:14 AM, Bjorn Helgaas wrote:
> > CRS SV is optional, so the code has to work when it's absent. But we
> > can tell whether it's supported, so if we need to, we can do something
> > different when it's absent.
>
> Let us know if you want to work on this or not. Otherwise, I'll add
> to the list of things I'm doing.
On my side (powerpc) I'll make sure we do get ffff's and that our retry
timeouts aren't too high. I just need to makes sure we don't end up
triggering an EEH failure on the timeout though.
Cheers,
Ben.
prev parent reply other threads:[~2018-03-22 22:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-22 4:03 PCIe resets/restore and lack of CRS wait Benjamin Herrenschmidt
2018-03-22 4:36 ` okaya
2018-03-22 5:12 ` Benjamin Herrenschmidt
2018-03-22 6:24 ` Benjamin Herrenschmidt
2018-03-22 11:25 ` okaya
2018-03-22 13:46 ` Benjamin Herrenschmidt
2018-03-22 13:58 ` Sinan Kaya
2018-03-22 14:14 ` Bjorn Helgaas
2018-03-22 17:54 ` Sinan Kaya
2018-03-22 22:02 ` Benjamin Herrenschmidt [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=1521756164.16434.319.camel@kernel.crashing.org \
--to=benh@kernel.crashing.org \
--cc=bhelgaas@google.com \
--cc=helgaas@kernel.org \
--cc=linux-pci-owner@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=michael.neuling@au1.ibm.com \
--cc=okaya@codeaurora.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 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.