From: David Laight <David.Laight@ACULAB.COM>
To: 'Petr Mladek' <pmladek@suse.com>,
Sergey Senozhatsky <senozhatsky@chromium.org>
Cc: John Ogness <john.ogness@linutronix.de>,
Peter Geis <pgwipeout@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
"open list:ARM/Rockchip SoC..."
<linux-rockchip@lists.infradead.org>
Subject: RE: [BUG] Threaded printk breaks early debugging
Date: Mon, 13 Jun 2022 16:11:19 +0000 [thread overview]
Message-ID: <c81870cef50f4e1fac5083f0b780983d@AcuMS.aculab.com> (raw)
In-Reply-To: <YqcN9mH/aVwBoIMQ@alley>
From: Petr Mladek
> Sent: 13 June 2022 11:14
...
> Another interesting alternative is the Peter Zijlstra's mode
> where all messages are printed to the console "immediately".
> They are serialized only by the CPU-reentrant lock.
>
> This mode is not good for production system. But it might
> be good for debugging. The good thing is that the behavior
> is well defined.
ISTM that all messages should be output (even if this means
that cpu spin waiting for a serial console) until userspace
has a chance to set an option to change the behaviour.
Oh, and can someone stop the distros hiding the console output.
I want to see the 'oops' traceback when I break the kernel!
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
next prev parent reply other threads:[~2022-06-13 18:59 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-10 12:48 [BUG] Threaded printk breaks early debugging Peter Geis
2022-06-10 15:05 ` John Ogness
2022-06-10 15:34 ` Peter Geis
2022-06-12 2:57 ` Sergey Senozhatsky
2022-06-12 13:30 ` Peter Geis
2022-06-12 23:08 ` John Ogness
2022-06-12 23:30 ` Peter Geis
2022-06-13 2:23 ` John Ogness
2022-06-13 15:11 ` Petr Mladek
2022-06-13 22:20 ` Peter Geis
2022-06-14 8:38 ` Petr Mladek
2022-06-13 11:24 ` Petr Mladek
2022-06-12 3:13 ` Sergey Senozhatsky
2022-06-12 23:02 ` John Ogness
2022-06-13 3:49 ` Sergey Senozhatsky
2022-06-13 8:30 ` John Ogness
2022-06-13 9:05 ` Sergey Senozhatsky
2022-06-13 10:14 ` Petr Mladek
2022-06-13 16:11 ` David Laight [this message]
2022-06-14 8:37 ` Petr Mladek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c81870cef50f4e1fac5083f0b780983d@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=john.ogness@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=pgwipeout@gmail.com \
--cc=pmladek@suse.com \
--cc=senozhatsky@chromium.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox