Re: [RFC/PATCH] Make printk work for really early debugging

[Andrew Morton <akpm@osdl.org>]

Michael Ellerman <michael@ellerman.id.au> wrote:
>
> Currently printk is no use for early debugging because it refuses to actually
>  print anything to the console unless cpu_online(smp_processor_id()) is true.
> 
>  The stated explanation is that console drivers may require per-cpu resources,
>  or otherwise barf, because the system is not yet setup correctly. Fair enough.
> 
>  However some console drivers might be quite happy running early during boot,
>  in fact we have one, and so it'd be nice if printk understood that.
> 
>  So I add a flag (which I would have called CON_BOOT, but that's taken) called
>  CON_ANYTIME, which indicates that a console is happy to be called anytime,
>  even if the cpu is not yet online.
> 
>  Tested on a Power 5 machine, with both a CON_ANYTIME driver and a bogus
>  console driver that BUG()s if called while offline. No problems AFAICT.
>  Built for i386 UP & SMP.

hm, OK.  But iirc is was just one silly ia64 console driver which had this
problem.  It might be better to make the new behaviour be the default and mark
the ia64 driver CON_NEEDS_CPU_ONLINE or something.

No?

Or go through and audit the drivers and sprinkle CON_ANYTIME in all the
safe ones, maybe.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/