From: rostedt@goodmis.org (Steven Rostedt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3] printk: add option to print cpu id
Date: Mon, 6 Aug 2012 09:39:17 -0400 [thread overview]
Message-ID: <20120806133917.GF16873@home.goodmis.org> (raw)
In-Reply-To: <CAFm5wm1SSmbdi09hc1Qo1eHw5Tc0vbMf1hWuNw-cjZEEx3jX5w@mail.gmail.com>
On Fri, Aug 03, 2012 at 03:48:26PM -0700, Pandita, Vikram wrote:
> On Fri, Aug 3, 2012 at 3:36 PM, Greg KH <gregkh@linuxfoundation.org> wrote:
> > On Fri, Aug 03, 2012 at 03:25:17PM -0700, Pandita, Vikram wrote:
> >> >> This was something that got used internally and helped at times.
> >> >
> >> > Could you have used the trace point instead?
> >>
> >> As i understood the trace_prink(), one would need to modify existing
> >> printk -> trace_printk. Is my understanding correct?
> >
> > No, you should just be able to watch the tracepoint, right?
>
> yes.
> Assumption being you know _EXACTLY_ what code piece to watch for.
> Which may not be the case all times.
But it traces all printks.
# echo 1 > /sys/kernel/debug/tracing/events/printk/console/enable
# mount /home/rostedt
# cat /sys/kernel/debug/tracing/trace
# tracer: nop
#
# entries-in-buffer/entries-written: 2/2 #P:4
#
# _-----=> irqs-off
# / _----=> need-resched
# | / _---=> hardirq/softirq
# || / _--=> preempt-depth
# ||| / delay
# TASK-PID CPU# |||| TIMESTAMP FUNCTION
# | | | |||| | |
modprobe-2707 [002] d..1 97.079458: console: [ 95.816945] NFS: Registering the id_resolver key type
modprobe-2707 [002] d..1 97.084534: console: [ 95.822038] Key type id_resolver registered
If you wanted this from boot up, you can just add to the kernel command line:
trace_event=console
-- Steve
next prev parent reply other threads:[~2012-08-06 13:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-03 16:56 [PATCH v3] printk: add option to print cpu id Vikram Pandita
2012-08-03 17:54 ` Andi Kleen
2012-08-03 18:25 ` Pandita, Vikram
2012-08-03 20:08 ` Aaro Koskinen
2012-08-03 21:24 ` Pandita, Vikram
2012-08-03 21:59 ` Greg KH
2012-08-03 22:07 ` Pandita, Vikram
2012-08-03 22:13 ` Greg KH
2012-08-03 22:25 ` Pandita, Vikram
2012-08-03 22:36 ` Greg KH
2012-08-03 22:48 ` Pandita, Vikram
2012-08-06 13:39 ` Steven Rostedt [this message]
2012-08-04 8:51 ` Russell King - ARM Linux
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=20120806133917.GF16873@home.goodmis.org \
--to=rostedt@goodmis.org \
--cc=linux-arm-kernel@lists.infradead.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