[PATCH] nvme: Boot as soon as the boot controller has been probed

[Greg KH]

On Sun, Nov 08, 2020 at 11:13:11AM -0800, Sagi Grimberg wrote:
> 
> > The following two issues have been introduced by commit 1811977568e0
> > ("nvme/pci: Use async_schedule for initial reset work"):
> > - The boot process waits until all NVMe controllers have been probed
> >    instead of only waiting until the boot controller has been probed.
> >    This slows down the boot process.
> > - Some of the controller probing work happens asynchronously without
> >    the device core being aware of this.
> > 
> > Hence this patch that makes all probing work happen from nvme_probe()
> > and that tells the device core to probe multiple NVMe controllers
> > concurrently by setting PROBE_PREFER_ASYNCHRONOUS.
> 
> This would make the controller instance inconsistent across reboots
> which is annoying for some users.

Then they should use persistent device names, as that is what they are
there for :)

Bus naming persistance is not a thing, we have BIOSes that love to
renumber PCI busses every other boot quite frequently.  If you have such
whacky hardware, fix this in userspace which is where it has been done
for a while now.

thanks,

greg k-h