[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <321c6d7d-b8e6-9b8d-91e5-a4f748acaa8e@codeaurora.org>
Date: Fri, 1 Jun 2018 11:10:20 -0400
From: Sinan Kaya <okaya@...eaurora.org>
To: "Alex G." <mr.nuke.me@...il.com>, bhelgaas@...gle.com
Cc: alex_gagniuc@...lteam.com, austin_bolen@...l.com,
shyam_iyer@...l.com, keith.busch@...el.com,
linux-pci@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH v2] PCI: Check for PCIe downtraining conditions
On 6/1/2018 11:06 AM, Alex G. wrote:
> On 06/01/2018 10:03 AM, Sinan Kaya wrote:
>> On 6/1/2018 11:01 AM, Alexandru Gagniuc wrote:
>>> + /* Multi-function PCIe share the same link/status. */
>>> + if (PCI_FUNC(dev->devfn) != 0)
>>> + return;
>>
>> How about virtual functions?
>
> I have almost no clue about those. Is your concern that we might end up
> printing more than our fair share of link statuses?
Yes, struct pci_dev also has a flag called is_virtfn that you should bail out
here too.
>
> Alex
>
>
--
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.
Powered by blists - more mailing lists