From: Sinan Kaya <okaya@codeaurora.org>
To: Jon Masters <jcm@redhat.com>, helgaas@kernel.org
Cc: linux-kernel@vger.kernel.org, linux-pci@vger.kernel.org
Subject: Re: FLR on AER
Date: Thu, 22 Feb 2018 08:57:21 -0500 [thread overview]
Message-ID: <372f63b2-2739-51fe-8959-3c5a0fecc29e@codeaurora.org> (raw)
In-Reply-To: <75DE2522-5DDC-4852-BE38-F7EB53691196@redhat.com>
On 2/22/2018 8:21 AM, Jon Masters wrote:
> Hi Bjorn,
>
> It looks like the AER driver won’t do a device FLR but instead will default to progressively bigger hammers. Am I missing something?
>
AFAIK, AER driver does a secondary bus reset only if it observes a FATAL error. In order to
issue an FLR, driver needs to access the endpoint config space. Since there is a FATAL error,
this is not possible as PCI link is unreliable or probably gone.
> Jon.
>
--
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.
prev parent reply other threads:[~2018-02-22 13:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-22 13:21 FLR on AER Jon Masters
2018-02-22 13:57 ` Sinan Kaya [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=372f63b2-2739-51fe-8959-3c5a0fecc29e@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=helgaas@kernel.org \
--cc=jcm@redhat.com \
--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;
as well as URLs for NNTP newsgroup(s).