Hi Russell, On Mon, Oct 19, 2015 at 5:35 PM, Russell King - ARM Linux <li...@arm.linux.org.uk> wrote: >> > What you can do is print those devices which have failed to probe at >> > late_initcall() time - possibly augmenting that with reports from >> > subsystems showing what resources are not available, but that's only >> > a guide, because of the "it might or might not be in a kernel module" >> > problem. >> >> Well, adding those reports would give you a changelog similar to the >> one in this series... > > I'm not sure about that, because what I was thinking of is adding > a flag which would be set at late_initcall() time prior to running > a final round of deferred device probing.
Which round is the final round? That's the one which didn't manage to bind any new devices to drivers, which is something you only know _after_ the round has been run. So I think we need one extra round to handle this. > This flag would then be used in a deferred_warn() printk function > which would normally be silent, but when this flag is set, it would > print the reason for the deferral - and this would replace (or be > added) to the subsystems and drivers which return -EPROBE_DEFER. > > That has the effect of hiding all the deferrals up until just before > launching into userspace, which should then acomplish two things - > firstly, getting rid of the rather useless deferred messages up to > that point, and secondly printing the reason why the remaining > deferrals are happening. > > That should be a small number of new lines plus a one-line change > in subsystems and drivers. Apart from the extra round we probably can't get rid of, that sounds OK to me. Gr{oetje,eeting}s, Geert -- Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@linux-m68k.org In personal conversations with technical people, I call myself a hacker. But when I'm talking to journalists I just say "programmer" or something like that. -- Linus Torvalds -- To unsubscribe from this list: send the line "unsubscribe linux-clk" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html