On 4/20/2018 2:55 AM, Greg KH wrote:
> 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.
It looks like the commit 523184972b28 ("vfio/pci: Virtualize Maximum Payload Size")
is already applied for 4.9.94.
Go ahead and apply commit cf0d53ba4947 ("vfio/pci: Virtualize Maximum Read Request
Size") for 4.9.y.
[detached HEAD 2ee0ebb] vfio/pci: Virtualize Maximum Read Request Size
Author: Alex Williamson <alex.williamson@xxxxxxxxxx>
Date: Mon Oct 2 12:39:10 2017 -0600
1 file changed, 26 insertions(+), 3 deletions(-)
I'll take a look at 4.4.y and check with Alex if these can be backported or not.
>
> 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
>
--
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.