From: Greg KH <gregkh@linuxfoundation.org>
To: Sinan Kaya <okaya@codeaurora.org>
Cc: stable@vger.kernel.org, Keith Busch <keith.busch@intel.com>,
Bjorn Helgaas <bhelgaas@google.com>
Subject: Re: Please apply commit 821cdad5c46c to v4.9.y
Date: Fri, 27 Apr 2018 09:09:43 +0200 [thread overview]
Message-ID: <20180427070943.GD4931@kroah.com> (raw)
In-Reply-To: <dbf0a565-e591-1268-781c-af35962137d9@codeaurora.org>
On Thu, Apr 26, 2018 at 04:34:50PM -0400, Sinan Kaya wrote:
> Hi Greg,
>
> Upstream commit 821cdad5c46c ("PCI: Wait up to 60 seconds for
> device to become ready after FLR") fixes a virtualization issue
> for Intel 750 NVMe drive and potentially other PCIe devices taking
> longer to recover from functional resets.
>
> problem description below from the commit:
>
> 'Sporadic reset issues have been observed with an Intel 750 NVMe drive while
> assigning the physical function to the guest machine. The sequence of
> events observed is as follows:
>
> - perform a Function Level Reset (FLR)
> - sleep up to 1000ms total
> - read ~0 from PCI_COMMAND (CRS completion for config read)
> - warn that the device didn't return from FLR
> - touch the device before it's ready
> - device drops config writes when we restore register settings (there's
> no mechanism for software to learn about CRS completions for writes)
> - incomplete register restore leaves device in inconsistent state
> - device probe fails because device is in inconsistent state
>
> After reset, an endpoint may respond to config requests with Configuration
> Request Retry Status (CRS) to indicate that it is not ready to accept new
> requests. See PCIe r3.1, sec 2.3.1 and 6.6.2.'
>
> Please apply commit 821cdad5c46c to fix the resulting regression.
Looks good, but it's not really a "regression" as it didn't work at all
before this patch :)
Now queued up.
greg k-h
prev parent reply other threads:[~2018-04-27 7:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-26 20:34 Please apply commit 821cdad5c46c to v4.9.y Sinan Kaya
2018-04-27 7:09 ` Greg KH [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=20180427070943.GD4931@kroah.com \
--to=gregkh@linuxfoundation.org \
--cc=bhelgaas@google.com \
--cc=keith.busch@intel.com \
--cc=okaya@codeaurora.org \
--cc=stable@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).