From: Tadeusz Struk <tadeusz.struk@intel.com>
To: Don Dutile <ddutile@redhat.com>
Cc: bhelgaas@google.com, linux-kernel@vger.kernel.org,
linux-pci@vger.kernel.org
Subject: Re: [PATCH] PCI: Make pci_find_upstream_pcie_bridge() handle non PCIE VFs well
Date: Wed, 09 Jan 2013 10:27:33 +0000 [thread overview]
Message-ID: <50ED4615.1040204@intel.com> (raw)
In-Reply-To: <50EC51E3.6070306@redhat.com>
On 01/08/2013 05:05 PM, Don Dutile wrote:
> (a) no such thing as a non-PCIe VF -- all VFs
> are PCIe-based.
The sriov spec says that a VF doesn't necessarily has to have PCIE cap:
"3.5 PCI Express Capability:
...
PFs and VFs are required to implement this capability ... subject to
the exceptions and additional requirements described below"
> (b) code says to return null if VF doesn't have PCIe cap,
> but the code checks if pdev is VF and if PF is PCIe,
> which it must be! ...
You are right, I should rather check if the VF is not a pcie.
> nack until a better &/or matching explanation of what
> the real problem is, and what the solution is trying to do.
The problem is that I do have a device where VFs are not PCIE and I get this nasty warning.
For now I have a workaround, but it would be nice it Linux would support non PCIE VFs.
Thanks,
T
next prev parent reply other threads:[~2013-01-09 10:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-08 14:32 [PATCH] PCI: Make pci_find_upstream_pcie_bridge() handle non PCIE VFs well tadeusz.struk
2013-01-08 17:05 ` Don Dutile
2013-01-09 10:27 ` Tadeusz Struk [this message]
2013-01-09 16:32 ` Don Dutile
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=50ED4615.1040204@intel.com \
--to=tadeusz.struk@intel.com \
--cc=bhelgaas@google.com \
--cc=ddutile@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.