mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Randy Dunlap <rdunlap@infradead.org>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>,
	John Ogness <john.ogness@linutronix.de>,
	Petr Mladek <pmladek@suse.com>, Marco Elver <elver@google.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] printk: allow direct console printing to be enabled always
Date: Sat, 18 Jun 2022 17:30:44 -0700	[thread overview]
Message-ID: <f1eb20d1-6762-dc82-058a-cf27936bc0c6@infradead.org> (raw)
In-Reply-To: <20220617133847.27517-1-Jason@zx2c4.com>



On 6/17/22 06:38, Jason A. Donenfeld wrote:
> diff --git a/Documentation/admin-guide/kernel-parameters.txt b/Documentation/admin-guide/kernel-parameters.txt
> index 8090130b544b..a960c47a2002 100644
> --- a/Documentation/admin-guide/kernel-parameters.txt
> +++ b/Documentation/admin-guide/kernel-parameters.txt
> @@ -4389,6 +4389,14 @@
>  	printk.time=	Show timing data prefixed to each printk message line
>  			Format: <bool>  (1/Y/y=enable, 0/N/n=disable)
>  
> +	printk.always_direct=
> +			Rather than using kthreads for printk output, always
> +			write to the console immediately. This has performance
> +			implications, but will result in a more faithful
> +			ordering and interleaving with other processes writing
> +			to the console.
> +			Format: <bool>  (1/Y/y=enable, 0/N/n=disable)

or:

+			Format: <bool>  (1/Y/y/T/t/on=enable, 0/N/n/F/f/off=disable)

-- 
~Randy

  reply	other threads:[~2022-06-19  0:31 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-17 13:23 5.19 printk breaks message ordering Jason A. Donenfeld
2022-06-17 13:37 ` Jason A. Donenfeld
2022-06-17 13:38   ` [PATCH] printk: allow direct console printing to be enabled always Jason A. Donenfeld
2022-06-19  0:30     ` Randy Dunlap [this message]
2022-06-19  8:37       ` Jason A. Donenfeld
2022-06-19 11:05     ` John Ogness
2022-06-19 20:39       ` Jason A. Donenfeld
2022-06-19 20:43         ` [PATCH v2] " Jason A. Donenfeld
2022-06-19 23:17           ` John Ogness
2022-06-19 23:28             ` Jason A. Donenfeld
2022-06-19 23:33               ` [PATCH v3] " Jason A. Donenfeld
2022-06-20 16:58                 ` Petr Mladek
2022-06-20 17:03                   ` Jason A. Donenfeld
2022-06-21  9:43                   ` David Laight
2022-06-21  9:59                 ` Jason A. Donenfeld
2022-06-22 12:55                   ` Jason A. Donenfeld
2022-06-20  4:04             ` [PATCH v2] " David Laight
2022-06-20  5:17             ` Sergey Senozhatsky
2022-06-20  7:56               ` Jason A. Donenfeld
2022-06-21  1:34                 ` Sergey Senozhatsky
2022-06-21 21:47               ` John Ogness
2022-06-17 14:21 ` 5.19 printk breaks message ordering Petr Mladek
2022-06-17 14:41   ` Jason A. Donenfeld
2022-06-17 15:01   ` David Laight
2022-06-19  8:15     ` John Ogness
2022-06-19 14:24       ` David Laight

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=f1eb20d1-6762-dc82-058a-cf27936bc0c6@infradead.org \
    --to=rdunlap@infradead.org \
    --cc=Jason@zx2c4.com \
    --cc=elver@google.com \
    --cc=john.ogness@linutronix.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pmladek@suse.com \
    /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

all inboxes | Powered by JetHome®