From: Sinan Kaya <okaya@codeaurora.org>
To: Alex Williamson <alex.williamson@redhat.com>
Cc: linux-pci@vger.kernel.org, timur@codeaurora.org,
cov@codeaurora.org, vikrams@codeaurora.org,
Lorenzo.Pieralisi@arm.com, linux-arm-msm@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH V3 2/2] PCI: handle CRS returned by device after FLR
Date: Wed, 1 Mar 2017 12:31:49 -0500 [thread overview]
Message-ID: <76938ac9-d898-1aa5-530c-d106584202d5@codeaurora.org> (raw)
In-Reply-To: <fa4f3b57-dccc-c64a-0787-1ecd3687534f@codeaurora.org>
On 2/21/2017 9:37 PM, Sinan Kaya wrote:
>> SR-IOV spec rev 1.1, 3.4.1.1 & 3.4.1.2, Vendor ID and Device ID fields
>> for the VF return 0xFFFF when read. The "Virtualization Intermediary"
>> is supposed to use the vendor ID from the PF and the device ID defined
>> in the PF SR-IOV capability.
>
> Interesting. Since lspci was showing the correct vendor id and device id, I
> assumed that it is coming from offset 0.
>
> Maybe, the right thing is to figure out if this is a virtual function or not.
> If it is a physical function, check the CRS first before reading the command
> register in the existing loop.
>
>
I went back and read the spec for CRS in FLR case one more time. We are required
to wait up to 1 seconds if the device is sending CRS. The current code seems to
be already handling this delay.
--
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:[~2017-03-01 17:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-03 5:36 [PATCH V3 0/2] PCI: add CRS support after hot reset and FLR Sinan Kaya
2016-10-03 5:36 ` [PATCH V3 1/2] PCI: add CRS support to error handling path Sinan Kaya
2016-11-10 18:39 ` Sinan Kaya
2016-10-03 5:37 ` [PATCH V3 2/2] PCI: handle CRS returned by device after FLR Sinan Kaya
2017-02-21 17:04 ` Sinan Kaya
2017-02-21 20:51 ` Alex Williamson
2017-02-22 2:37 ` Sinan Kaya
2017-03-01 17:31 ` 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=76938ac9-d898-1aa5-530c-d106584202d5@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=Lorenzo.Pieralisi@arm.com \
--cc=alex.williamson@redhat.com \
--cc=cov@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=timur@codeaurora.org \
--cc=vikrams@codeaurora.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
all inboxes | Powered by JetHome®