linux-pci.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sinan Kaya <okaya@codeaurora.org>
To: Bjorn Helgaas <helgaas@kernel.org>
Cc: Benjamin Herrenschmidt <benh@kernel.crashing.org>,
	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: Thu, 22 Mar 2018 12:54:01 -0500	[thread overview]
Message-ID: <6aec45f1-74d9-d36f-7169-0c91733985e3@codeaurora.org> (raw)
In-Reply-To: <20180322141402.GA242245@bhelgaas-glaptop.roam.corp.google.com>

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.

Sinan

-- 
Sinan Kaya
Qualcomm Datacenter Technologies, Inc. as an affiliate of Qualcomm Technologies, Inc.
Qualcomm Technologies, Inc. is a member of the Code Aurora Forum, a Linux Foundation Collaborative Project.

  reply	other threads:[~2018-03-22 17:54 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 [this message]
2018-03-22 22:02                 ` Benjamin Herrenschmidt

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=6aec45f1-74d9-d36f-7169-0c91733985e3@codeaurora.org \
    --to=okaya@codeaurora.org \
    --cc=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 \
    /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).