From: Andrew Morton <akpm@linux-foundation.org>
To: Ravikiran G Thirumalai <kiran@scalex86.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] printk: Print cpuid along with the timestamp with CONFIG_PRINTK_TIME
Date: Thu, 18 Sep 2008 12:51:23 -0700 [thread overview]
Message-ID: <20080918125123.1a76978f.akpm@linux-foundation.org> (raw)
In-Reply-To: <20080918193720.GA21915@localdomain>
On Thu, 18 Sep 2008 12:37:20 -0700
Ravikiran G Thirumalai <kiran@scalex86.org> wrote:
> I found it useful to have the cpuid of the printing cpu along with the
> timestamp -- especially while debugging hangs during bootups.
>
> I don't know why this hasn't been implemened in the kernel yet, and
> cannot think of a strong reason not to have it. Yes, the cpuid prefix will
> take 5 more characters per line, but having the cpuid info is worth it,
> I think.
>
> Thanks,
> Kiran
>
> ---
>
>
> Add cpuid information to printk if CONFIG_PRINTK_TIME is enabled.
> This information is useful to debug hangs and bootup issues.
>
> Signed-off-by: Ravikiran Thirumalai <kiran@scalex86.org>
>
> Index: linux-git/kernel/printk.c
> ===================================================================
> --- linux-git.orig/kernel/printk.c 2008-09-16 15:37:48.000000000 -0700
> +++ linux-git/kernel/printk.c 2008-09-18 12:27:10.489662938 -0700
> @@ -739,9 +739,10 @@ asmlinkage int vprintk(const char *fmt,
>
> t = cpu_clock(printk_cpu);
> nanosec_rem = do_div(t, 1000000000);
> - tlen = sprintf(tbuf, "[%5lu.%06lu] ",
> + tlen = sprintf(tbuf, "[%5lu.%06lu:%d] ",
> (unsigned long) t,
> - nanosec_rem / 1000);
> + nanosec_rem / 1000,
> + printk_cpu);
>
> for (tp = tbuf; tp < tbuf + tlen; tp++)
> emit_log_char(*tp);
Yes, I guess it could be useful sometimes. otoh anyone who is down at
that level of detail and is using printk to debug something can add
their own %d/smp_processor_id().
Your patch illogically ties the cpu-id-printing feature to the
printk.time feature. I guess that's liveable with, but
Documentation/kernel-parameters.txt should be updated.
Anyone who was parsing that output might get a shock, but that's
liveable with too. Probably their parser will continue to work anwyay.
I don't know whether the usefulness of this feature outweighs its
various costs. Input is sought.
next prev parent reply other threads:[~2008-09-18 19:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 19:37 [PATCH] printk: Print cpuid along with the timestamp with CONFIG_PRINTK_TIME Ravikiran G Thirumalai
2008-09-18 19:51 ` Andrew Morton [this message]
2008-09-19 0:35 ` Ravikiran G Thirumalai
2008-09-19 17:15 ` Marcin Slusarz
2008-09-19 18:39 ` Ravikiran G Thirumalai
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=20080918125123.1a76978f.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=kiran@scalex86.org \
--cc=linux-kernel@vger.kernel.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