Christoph Hellwig wrote: > On Mon, Jul 14, 2025 at 04:20:03PM +0200, Lukas Wunner wrote: > > I guess what happens in your case is, *after* initial probing has > > concluded and user space is up and running, a driver is unbound > > from the device and another driver is subsequently re-bound. > > E.g. "nvme" is unbound and "virtio-pci" is bound instead. > > How? This is a non-modular simply kernel running on kvm. There > should be no re-binding, and binding nvme devices to virtio of course > also doesn't make sense. I too could have swore I see async behavior with cxl_pci. I believe this patch is only affecting async behavior when the driver is loaded before initial arrival of the PCI device. For the typical modular driver case the late arriving driver also arranges async probing. Lo and behold on current upstream: [ 13.002750] __driver_attach: pci 0000:35:00.0: probing driver cxl_pci asynchronously ...so this patch is only a change in behavior for built-in drivers loaded before PCI initial scan afaics.
