From: Ingo Molnar <mingo@elte.hu>
To: Frederic Weisbecker <fweisbec@gmail.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Peter Zijlstra <a.p.zijlstra@chello.nl>,
Steven Rostedt <rostedt@goodmis.org>,
tglx@linutronix.de, Jason Baron <jbaron@redhat.com>,
"Frank Ch. Eigler" <fche@redhat.com>,
Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>,
KOSAKI Motohiro <kosaki.motohiro@jp.fujitsu.com>,
Lai Jiangshan <laijs@cn.fujitsu.com>,
Jiaying Zhang <jiayingz@google.com>,
Michael Rubin <mrubin@google.com>,
Martin Bligh <mbligh@google.com>,
Michael Davidson <md@google.com>
Subject: Re: [PATCH 0/2 v2] Syscalls tracing
Date: Fri, 13 Mar 2009 17:17:49 +0100 [thread overview]
Message-ID: <20090313161749.GA3203@elte.hu> (raw)
In-Reply-To: <20090313155541.GA15481@elte.hu>
* Ingo Molnar <mingo@elte.hu> wrote:
>
> * Frederic Weisbecker <fweisbec@gmail.com> wrote:
>
> > On Fri, Mar 13, 2009 at 03:42:10PM +0100, Frederic Weisbecker wrote:
> > > tracing/syscalls: core infrastructure to trace syscalls
> > >
> > > This new iteration addresses a good part of the previous reviews.
> >
> >
> > Ah I just discovered that you applied the previous version
> > today. But the v2 is not a delta :-s
> >
> > I can rebase them but not until Sunday.
>
> No problem, i'll deltify them and will have a look.
Ok, i did the deltas, tidied them up and put them into
tip:tracing/syscalls.
Nice stuff! Here's some sample output:
aldebaran:/debug/tracing> head trace
# tracer: syscall
#
# TASK-PID CPU# TIMESTAMP FUNCTION
# | | | | |
<...>-4405 [003] 188.452934: sys_dup2(oldfd: a, newfd: 1)
<...>-4405 [003] 188.452939: sys_dup2 -> 0x1
<...>-4405 [003] 188.452940: sys_fcntl(fd: a, cmd: 1, arg: 0)
<...>-4405 [003] 188.452941: sys_fcntl -> 0x1
<...>-4405 [003] 188.452942: sys_close(fd: a)
<...>-4405 [003] 188.452943: sys_close -> 0x0
A suggestion:
- Would be nice for all the registered syscalls to show up
under /debug/events/syscalls/, one directory per syscall,
with an 'enable' and a 'format' file as well.
And a bugreport:
- when using function_graph (after having used the syscall
tracer) i dont see graph traces anymore - only the syscall
trace entries:
# tracer: function_graph
#
# CPU DURATION FUNCTION CALLS
# | | | | | | |
##### CPU 9 buffer started ####
at-spi-registry-3063 [009] 322.915058: sys_read -> 0x5a8
at-spi-registry-3063 [009] 322.915059: sys_write(fd: 6, buf: 632840, count: 5a8)
at-spi-registry-3063 [009] 322.915062: sys_write -> 0x5a8
at-spi-registry-3063 [009] 322.915062: sys_read(fd: 4, buf: 632840, count: 40000)
That's not intended, right?
Ingo
next prev parent reply other threads:[~2009-03-13 16:18 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-13 14:42 [PATCH 0/2 v2] Syscalls tracing Frederic Weisbecker
2009-03-13 14:42 ` [PATCH 1/2 v2] tracing/syscalls: core infrastructure for syscalls tracing Frederic Weisbecker
2009-03-13 16:09 ` [tip:tracing/syscalls] tracing/syscalls: core infrastructure for syscalls tracing, enhancements Frederic Weisbecker
2009-03-15 3:51 ` [PATCH 1/2 v2] tracing/syscalls: core infrastructure for syscalls tracing Andrew Morton
2009-03-15 4:59 ` Ingo Molnar
2009-03-15 8:02 ` Andrew Morton
2009-03-15 16:17 ` Frederic Weisbecker
2009-04-06 21:55 ` Tony Luck
2009-04-06 22:12 ` Frederic Weisbecker
2009-04-07 0:30 ` Steven Rostedt
2009-04-08 18:40 ` [PATCH] tracing/syscalls: use a dedicated file header Frederic Weisbecker
2009-04-08 19:36 ` Luck, Tony
2009-04-08 22:44 ` Steven Rostedt
2009-04-08 22:51 ` Luck, Tony
2009-04-08 23:02 ` Steven Rostedt
2009-04-08 23:08 ` Luck, Tony
2009-04-08 23:32 ` Steven Rostedt
2009-04-08 23:32 ` Joe Perches
2009-04-09 0:15 ` [GIT PULL][PATCH] " Steven Rostedt
2009-04-09 4:36 ` [tip:tracing/urgent] " Frederic Weisbecker
2009-03-13 14:42 ` [PATCH 2/2 v2] tracing/syscalls: support for syscalls tracing on x86-64 Frederic Weisbecker
2009-03-13 16:09 ` [tip:tracing/syscalls] tracing/syscalls: support for syscalls tracing on x86 Frederic Weisbecker
2009-03-15 3:53 ` [PATCH 2/2 v2] tracing/syscalls: support for syscalls tracing on x86-64 Andrew Morton
2009-03-15 5:30 ` Ingo Molnar
2009-03-15 16:05 ` Frederic Weisbecker
2009-03-13 15:16 ` [PATCH 0/2 v2] Syscalls tracing Frederic Weisbecker
2009-03-13 15:55 ` Ingo Molnar
2009-03-13 16:17 ` Ingo Molnar [this message]
2009-03-15 15:25 ` Frederic Weisbecker
2009-03-13 16:47 ` Mathieu Desnoyers
2009-03-15 16:01 ` Frederic Weisbecker
2009-03-23 16:32 ` Mathieu Desnoyers
2009-03-23 19:27 ` Frederic Weisbecker
2009-03-23 19:40 ` Ingo Molnar
2009-03-23 20:37 ` Mathieu Desnoyers
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=20090313161749.GA3203@elte.hu \
--to=mingo@elte.hu \
--cc=a.p.zijlstra@chello.nl \
--cc=fche@redhat.com \
--cc=fweisbec@gmail.com \
--cc=jbaron@redhat.com \
--cc=jiayingz@google.com \
--cc=kosaki.motohiro@jp.fujitsu.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@polymtl.ca \
--cc=mbligh@google.com \
--cc=md@google.com \
--cc=mrubin@google.com \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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