From: Greg KH <greg@kroah.com>
To: Sinan Kaya <okaya@codeaurora.org>
Cc: stable@vger.kernel.org, Alex Williamson <alex.williamson@redhat.com>
Subject: Re: Please apply commit cf0d53ba4947 and 523184972b28 to v4.4.y, v4.9.y, v4.14.y
Date: Fri, 20 Apr 2018 08:55:09 +0200 [thread overview]
Message-ID: <20180420065509.GA4876@kroah.com> (raw)
In-Reply-To: <3dc65572-74c2-4f09-1729-8957c5f36ac9@codeaurora.org>
On Thu, Apr 19, 2018 at 01:07:29PM -0400, Sinan Kaya wrote:
> Hi Greg,
>
> Upstream commit cf0d53ba4947 ("vfio/pci: Virtualize Maximum Read Request
> Size") and commit 523184972b28 ("vfio/pci: Virtualize Maximum Payload Size")
> fixes nasty PCIe virtualization issues for platforms that support Maximum
> Payload Size bigger than 128.
>
> Issue shows up when a device is assigned to the guest machine as a passthrough.
> Guest machine configures the MPS/MRRS settings to values that are incompatible
> with the parent bridge device.
>
> This causes PCIe transaction timeouts and AER errors to be spilled in the host
> kernel.
>
> Please apply commit cf0d53ba4947 and 523184972b28 to all affected releases to
> fix the resulting regression.
The first patch does not apply to 4.4.y, and the second one does not
apply anywhere :(
Can you provide a series of backported patches that apply for me to
queue up?
thanks,
greg k-h
next prev parent reply other threads:[~2018-04-20 6:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-19 17:07 Please apply commit cf0d53ba4947 and 523184972b28 to v4.4.y, v4.9.y, v4.14.y Sinan Kaya
2018-04-19 17:21 ` Alex Williamson
2018-04-20 6:55 ` Greg KH [this message]
2018-04-20 16:47 ` Sinan Kaya
2018-04-20 16:56 ` Greg KH
2018-04-20 21:06 ` Sinan Kaya
2018-04-20 21:50 ` Alex Williamson
2018-04-22 7:20 ` Greg KH
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=20180420065509.GA4876@kroah.com \
--to=greg@kroah.com \
--cc=alex.williamson@redhat.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).