From: Peter Zijlstra <peterz@infradead.org>
To: Joe Lawrence <joe.lawrence@redhat.com>
Cc: linux-kernel@vger.kernel.org, Ingo Molnar <mingo@redhat.com>
Subject: Re: [PATCH 1/2] sched/debug: fix per-task line continuation for console
Date: Mon, 19 Mar 2018 21:17:23 +0100 [thread overview]
Message-ID: <20180319201723.GK4043@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <1521484555-8620-2-git-send-email-joe.lawrence@redhat.com>
On Mon, Mar 19, 2018 at 02:35:54PM -0400, Joe Lawrence wrote:
> When the SEQ_printf() macro prints to the console, it runs a simple
> printk() without KERN_CONT "continued" line printing. The result of
> this is oddly wrapped task info, for example:
>
> % echo t > /proc/sysrq-trigger
> % dmesg
> ...
> runnable tasks:
> ...
> [ 29.608611] I
> [ 29.608613] rcu_sched 8 3252.013846 4087 120
> [ 29.608614] 0.000000 29.090111 0.000000
> [ 29.608615] 0 0
> [ 29.608616] /
>
> Modify SEQ_printf to use pr_cont() for expected one-line results:
>
> % echo t > /proc/sysrq-trigger
> % dmesg
> ...
> runnable tasks:
> ...
> [ 106.716329] S cpuhp/5 37 2006.315026 14 120 0.000000 0.496893 0.000000 0 0 /
>
> Signed-off-by: Joe Lawrence <joe.lawrence@redhat.com>
> ---
> kernel/sched/debug.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/kernel/sched/debug.c b/kernel/sched/debug.c
> index 1ca0130ed4f9..50026aa2d81e 100644
> --- a/kernel/sched/debug.c
> +++ b/kernel/sched/debug.c
> @@ -32,7 +32,7 @@
> if (m) \
> seq_printf(m, x); \
> else \
> - printk(x); \
> + pr_cont(x); \
That used to work I think.. I think someone changed how printk() behaves
somewhere along the lines.
Does pr_cont("\n") DTRT? it seems like something weird.
next prev parent reply other threads:[~2018-03-19 20:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-19 18:35 [PATCH 0/2] small scheduler debug stat fixups Joe Lawrence
2018-03-19 18:35 ` [PATCH 1/2] sched/debug: fix per-task line continuation for console Joe Lawrence
2018-03-19 20:17 ` Peter Zijlstra [this message]
2018-03-19 20:43 ` Joe Lawrence
2018-03-20 8:08 ` Peter Zijlstra
2018-03-20 11:18 ` [tip:sched/urgent] sched/debug: Fix per-task line continuation for console output tip-bot for Joe Lawrence
2018-03-19 18:35 ` [PATCH 2/2] sched/debug: adjust newlines for better alignment Joe Lawrence
2018-03-20 11:19 ` [tip:sched/urgent] sched/debug: Adjust " tip-bot for Joe Lawrence
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=20180319201723.GK4043@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=joe.lawrence@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.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
Powered by JetHome