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

[Keith Busch]

On Sat, Nov 07, 2020 at 08:09:03PM -0800, Bart Van Assche 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.

Prior to that commit, the boot process didn't wait for anything at all
and missed the boot controller entirely.

> - Some of the controller probing work happens asynchronously without
>   the device core being aware of this.

Why is that an "issue"?

> 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.

Afaics, that setting just may let driver core do an async_schedule() for
the asynchronous part, but that's what we're already doing. ?