Re: [RFC PATCH 7/8] PCI/IOV: Initialize virtual functions in parallel

[sashiko-bot@kernel.org]

> Serial per-VF scanning and device addition dominate SR-IOV enable time at
> large VF counts, and a kexec-based live update re-creates every VF
> through this same loop. Distribute the per-VF work over the kernel's
> async machinery.
> 
> VF0 is added synchronously first because pci_iov_scan_device() writes the
> config fields shared by every VF only on the id == 0 pass and reads them
> locklessly afterwards. The rest are fanned out over async entries
> sharing an on-stack context with an atomic id cursor, scheduled on the
> PF's node with async_schedule_node_domain(). A worker that fails records
> the first error there and the enabling task unwinds every id descending;
> when several fail the temporally first errno is reported where the serial
> code reported the lowest failing id's, and nothing in-tree consumes the
> distinction.
> 
> [ ... ]
> past the failing id before unwinding them all. VF probes run in async
> context, where a synchronous request_module() WARNs.
> 
> Assisted-by: LLM
> Signed-off-by: Pavol Sakac <sakacpav@amazon.de>

Sashiko has reviewed this patch and found no issues. It looks great!

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260911-vfopt-s1-v1-0-693271dc0226@amazon.de?part=7