linux-kernel - Re: PCIe bus enumeration

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 04 Jul 2014 09:55:20 +0200
From:	Federico Vaga <federico.vaga@...il.com>
To:	Bjorn Helgaas <bhelgaas@...gle.com>
Cc:	"linux-pci@...r.kernel.org" <linux-pci@...r.kernel.org>,
	"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
	Michel Arruat <michel.arruat@...il.com>
Subject: Re: PCIe bus enumeration

> I assume these ports don't support hotplug.  If they *did* support
> hotplug, those ports would have to exist because they handle the
> hotplug events (presence detect, etc.)

I asked: yes, they do not support hotplug

> If you can collect the complete "lspci -vv" output from your machine
> (with a device plugged in, so we can see the port leading to it),
> that will help make this more concrete.  And maybe one with no
> devices plugged in, so we can see exactly what changes.

I attached two files with the output. I putted a card in slot 10 and 
took the output, then moved the card on slot 11 and took the output.

As you can see with diff the bridge behind the slot disappear when it 
is empty.

-- 
Federico Vaga
View attachment "lspci-slot11-emtpy-slot10-busy" of type "text/plain" (32179 bytes)

View attachment "lspci-slot11-busy-slot10-empty" of type "text/plain" (32308 bytes)