Re: [Ksummit-discuss] [TECH TOPIC] asynchronous printk

[David Woodhouse <dwmw2@infradead.org>]

[-- Attachment #1: Type: text/plain, Size: 1216 bytes --]

On Thu, 2016-07-21 at 07:59 +0200, Hannes Reinecke wrote:
> > If we do all this stuff, can we also try to clean up earlyprintk a
> > bit?  The whole earlyconsole mechanism is a mess, and switching over
> > to the non-early console is only somewhat functional.  I'd love to see
> > this all simplified: before there's any console at all available, just
> > buffer messages.  Then, when a console shows up, write the buffer out.
> > Then earlyprintk can work just like regular printk.
> > 
> Begging the question how one would debug failures during that time.
> The current earlyprintk stuff is at least able to print out _something_,
> so that you have some idea what went wrong.
> Without that things will become _really_ hard during board bringup.

No, you don't actually *delay* the console output. You still register
the console as soon as you physically can, but you just don't have all
that nasty special-casing of the "earlyprintk" nonsense; you just make
sure the standard console output is capable of working as early as you
need it to.

-- 
David Woodhouse                            Open Source Technology Centre
David.Woodhouse@intel.com                              Intel Corporation

[-- Attachment #2: smime.p7s --]
[-- Type: application/x-pkcs7-signature, Size: 5760 bytes --]