From: Randy Dunlap <rdunlap@infradead.org>
To: "he, bo" <bo.he@intel.com>
Cc: akpm@linux-foundation.org, mingo@elte.hu, a.p.zijlstra@chello.nl,
linux-kernel@vger.kernel.org, yanmin_zhang@linux.intel.com
Subject: Re: [PATCH] output the cpu number when printking.
Date: Sun, 23 Dec 2012 19:37:17 -0800 [thread overview]
Message-ID: <50D7CDED.4060308@infradead.org> (raw)
In-Reply-To: <1356316276.2385.7.camel@hebo>
On 12/23/12 18:31, he, bo wrote:
> From: "he, bo" <bo.he@intel.com>
>
> We often hit kernel panic issues on SMP machines because processes race
> on multiple cpu. By adding a new parameter printk.cpu, kernel prints
> cpu number at printk information line. It’s useful to debug what cpus
> are racing.
>
> Signed-off-by: he, bo <bo.he@intel.com>
> ---
> Documentation/kernel-parameters.txt | 4 ++++
> kernel/printk.c | 18 ++++++++++++++++--
> 2 files changed, 20 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/kernel-parameters.txt b/Documentation/kernel-parameters.txt
> index ddd84d6..ccd5266 100644
> --- a/Documentation/kernel-parameters.txt
> +++ b/Documentation/kernel-parameters.txt
> @@ -2378,6 +2378,10 @@ bytes respectively. Such letter suffixes can also be entirely omitted.
> printk.time= Show timing data prefixed to each printk message line
> Format: <bool> (1/Y/y=enable, 0/N/n=disable)
>
> + printk.cpu= Show cpu data prefixed to each printk message line
> + Format: <bool> (1/Y/y=enable, 0/N/n=disable)
> + printk.cpu takes effect only when printk.time=y.
Above line needs to be indented more (beginning under "Format:").
> +
> processor.max_cstate= [HW,ACPI]
> Limit processor to maximum C-state
> max_cstate=9 overrides any DMI blacklist limit.
> diff --git a/kernel/printk.c b/kernel/printk.c
> index 19c0d7b..873a226 100644
> --- a/kernel/printk.c
> +++ b/kernel/printk.c
> @@ -863,9 +863,14 @@ static bool printk_time;
> #endif
> module_param_named(time, printk_time, bool, S_IRUGO | S_IWUSR);
>
> +static bool printk_cpu = 1;
> +module_param_named(cpu, printk_cpu, bool, S_IRUGO | S_IWUSR);
> +
> static size_t print_time(u64 ts, char *buf)
> {
> unsigned long rem_nsec;
> + size_t len = 0;
> + int this_cpu;
>
> if (!printk_time)
> return 0;
> @@ -874,8 +879,17 @@ static size_t print_time(u64 ts, char *buf)
> return 15;
>
> rem_nsec = do_div(ts, 1000000000);
> - return sprintf(buf, "[%5lu.%06lu] ",
> - (unsigned long)ts, rem_nsec / 1000);
> +
> + if (printk_cpu) {
> + this_cpu = raw_smp_processor_id();
> + len = sprintf(buf, "[%5lu.%06lu,%u] ",
> + (unsigned long)ts, rem_nsec / 1000, this_cpu);
> + } else {
> + len = sprintf(buf, "[%5lu.%06lu] ",
> + (unsigned long)ts, rem_nsec / 1000);
> + }
> +
> + return len;
> }
>
> static size_t print_prefix(const struct log *msg, bool syslog, char *buf)
>
--
~Randy
next prev parent reply other threads:[~2012-12-24 3:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-24 2:31 [PATCH] output the cpu number when printking he, bo
2012-12-24 3:37 ` Randy Dunlap [this message]
2012-12-24 3:54 ` he, bo
2012-12-24 5:01 ` [PATCH V2] " he, bo
2012-12-24 17:55 ` Greg KH
2012-12-25 1:09 ` Yanmin Zhang
2012-12-26 17:50 ` Greg KH
2012-12-27 6:49 ` He, Bo
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=50D7CDED.4060308@infradead.org \
--to=rdunlap@infradead.org \
--cc=a.p.zijlstra@chello.nl \
--cc=akpm@linux-foundation.org \
--cc=bo.he@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=yanmin_zhang@linux.intel.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