From: Federico Vaga <federico.vaga@gmail.com>
To: Bjorn Helgaas <bhelgaas@google.com>
Cc: linux-pci@vger.kernel.org, linux-kernel@vger.kernel.org,
Michel Arruat <michel.arruat@gmail.com>
Subject: PCIe bus enumeration
Date: Thu, 03 Jul 2014 18:45:54 +0200 [thread overview]
Message-ID: <280883016.9onmf0miLq@pcbe13110.cern.ch> (raw)
Hello,
(I haven't a deep knowledge of the PCIe specification, maybe I'm just
missing something)
is there a way to force the PCI subsystem to assign a bus-number to
every PCIe bridge, even if there is nothing connected?
My aim is to have a bus enumeration constant and independent from what
I plugged on the system. So, I can associate a physical slot to linux
device address bb:dd.f. Is it possible?
I can do the mapping with a simple shell script by discovering the
"new" bus number, but I'm wondering if there is a way to have a
constant bus enumeration.
My Humble Observation
---------------------
It seems (to me) that for PCI the kernel assigns a bus-number to every
PCI bridges and sub-bridges even if there is nothing connected:
e.g. from lspci -t
[...]
+-1e.0-[04-05]----0c.0-[05]--
00:1e.0 PCI bridge: Intel Corporation 82801 PCI Bridge (rev 92)
04:0c.0 PCI bridge: Texas Instruments PCI2050 PCI-to-PCI Bridge (rev
02)
The behavior on PCIe seems different. When there is nothing plugged on
a bus, then the kernel doesn't assign any bus-number and it doesn't
detect any PCI-Bridge at all. So, when I reboot the system with a new
PCIe card the bus enumeration may change.
I tried to use the following pci kernel parameters:
assign-busses : because I want to force the kernel to re-enumerate the
busses, hopefully _all_ buses even if they are empty.
pcie_scan_all : not clear the explanation, but it sounds like it tells
to the kernel to inspect everything.
bfsort : because, maybe, for a bfsort it must assign a number to each
bridge at the same level before inspect the next one.
noacpi : in order to scan independently from BIOS information
The result is always the same (empty buses are not enumerated).
Thank you :)
--
Federico Vaga
next reply other threads:[~2014-07-03 16:45 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-03 16:45 Federico Vaga [this message]
2014-07-03 19:43 ` PCIe bus enumeration Bjorn Helgaas
2014-07-03 20:40 ` Federico Vaga
2014-07-03 22:04 ` Bjorn Helgaas
2014-07-04 7:55 ` Federico Vaga
2014-07-04 21:26 ` Bjorn Helgaas
2014-07-07 7:29 ` Federico Vaga
2014-07-07 17:34 ` Bjorn Helgaas
2014-07-08 7:15 ` Federico Vaga
2014-07-08 18:23 ` Bjorn Helgaas
2014-07-08 19:20 ` Federico Vaga
2014-07-08 20:27 ` Bjorn Helgaas
2014-08-07 14:59 ` Federico Vaga
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=280883016.9onmf0miLq@pcbe13110.cern.ch \
--to=federico.vaga@gmail.com \
--cc=bhelgaas@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=michel.arruat@gmail.com \
/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).