On Sat, Aug 18, 2018 at 01:37:35PM +1000, Benjamin Herrenschmidt wrote:
> As-is, what you have is a bit that is private to drivers/pci (why ?
> devices might be interested in knowing the device has been
> disconnected...)
It is private to drivers/pci because Greg wanted it so:
"> The flag is not intended for a device specific driver to use.
> The intention is for the pci bus driver to use it, so no additional
> work for other drivers.
But the driver can see this in the structure, so it will get used..."
https://spinics.net/lists/linux-pci/msg57744.html
"I applaud your attempt to make this "private" to the pci core, just
don't know if it really will work, or if it is worth it entirely..."
https://spinics.net/lists/linux-pci/msg58017.html
Greg is of the opinion that drivers should check for themselves whether
a device has been removed and he was happy that they are barred from
using PCI_DEV_DISCONNECTED. He believes that drivers should verify
for every read of mmio and config space that that the read value is not
0xffffffff (if that is an invalid value) and consider the device removed
if so:
"If you are worried about your device going away (and you have to),
then just check all reads and be fine with it. If you have values
that can be all 0xff, then just accept that as a valid value and
move to the next read where it can't be valid."
https://spinics.net/lists/linux-pci/msg70793.html
However Alex Gagniuc recently countered:
"The discussion is based on the wrong assumptions that reads are
symmetrical wrt to a device being present or not. However, completion
timeouts and unsupported requests blow that assumption right out of the
water. Best case scenario, you just waste a little more time waiting for
hardware IO. More common is to end up crashing the machine.
Greg's ideas work in a perfect world where PCI and PCIe are equivalent
at every level. And in that case, PCI_DEV_DISCONNECTED would have been
pure, 100% genuine Redmond bloatware. We wouldn't have gotten complaints
from Facebook and other industry players that it takes too damn long to
remove a device. We probably also wouldn't be seeing machines crash on
PCIe removal."
https://spinics.net/lists/linux-pci/msg74864.html
The reason I'm interested in PCI_DEV_DISCONNECTED is because hot-removing
an Apple Thunderbolt Ethernet adapter locks up the machine a due to the tg3
driver trying to access the removed device.
Now, tg3 does call pci_channel_offline() and refrains from accessing the
device if that returns true. If I make PCI_DEV_DISCONNECTED public and
check its value in pci_channel_offline(), I can hot-remove the Thunderbolt
Ethernet adapter without problems. I posted a patch for that 2 years ago:
https://spinics.net/lists/linux-pci/msg55601.html
Thus, I'd be more than happy if the PCI_DEV_DISCONNECTED state could be
folded into enum pci_channel_state as it would immediately fix Thunderbolt
hot-removal.
> Fundamentally both mean, from a driver perspective, two things.
>
> - One very important: break out of a loop that waits for a HW state to
> change because it won't
>
> - One an optimisation: don't bother with all those register updates
> bcs they're never going to reach your HW.
Right. PCI_DEV_DISCONNECTED was introduced by Intel on behalf of
Facebook. See slides 13 to 16 of this slide deck for the details:
http://files.opencompute.org/oc/public.php?service=files&t=4ff50715e3c1e273e02b694757b80d25&download
There's a graph on slide 16 showing the speedup achieved by
PCI_DEV_DISCONNECTED.
There's also a recording of that talk, the relevant segment is just
10 minutes:
https://youtu.be/GJ6B0xzgvlM?t=926
Thanks,
Lukas
