From: Mathieu Desnoyers <mathieu.desnoyers@polymtl.ca>
To: Ingo Molnar <mingo@elte.hu>
Cc: Josh Stone <jistone@redhat.com>, Li Zefan <lizf@cn.fujitsu.com>,
linux-kernel@vger.kernel.org, fweisbec@gmail.com,
laijs@cn.fujitsu.com, rostedt@goodmis.org, peterz@infradead.org,
jiayingz@google.com, mbligh@google.com,
Jason Baron <jbaron@redhat.com>
Subject: Re: [PATCH] tracing: Create generic syscall TRACE_EVENTs
Date: Wed, 19 Aug 2009 09:50:12 -0400 [thread overview]
Message-ID: <20090819135011.GA8674@Krystal> (raw)
In-Reply-To: <20090819130517.GB14215@elte.hu>
* Ingo Molnar (mingo@elte.hu) wrote:
>
> * Josh Stone <jistone@redhat.com> wrote:
>
> > On 08/18/2009 06:32 PM, Li Zefan wrote:
> > > It would be much better to see a sample output of these TRACE_EVENTs,
> > > so we'll see the what's the output if a syscall has less than 6 args.
> > >
> > > And I guess it should be "(%lx, %lx, ..., %lx)"? Otherwise I think we'll
> > > see some negative values.
> >
> > Thanks, you're right -- the args should be unsigned long. Whether they
> > are hex or decimal doesn't matter to me, but I guess that does make
> > pointers easier to spot.
> >
> > Here's some output that I get on x86_64:
> >
> > > # tail trace
> > > tail-1106 [000] 113218.474657: syscall_enter: NR 2 (7f2d34dd38f0, 0, 7f2d35009010, 5, 4, ffffffffffffffb0)
> > >
> > > tail-1106 [000] 113218.474809: syscall_enter: NR 5 (3, 7f2d35009040, 7f2d35009040, 5, 4, ffffffffffffffb0)
> > >
> > > tail-1106 [000] 113218.474855: syscall_enter: NR 9 (0, 50d3ad0, 1, 2, 3, 0)
> > >
> > > tail-1106 [000] 113218.474946: syscall_enter: NR 3 (3, 7f2d2f9a0000, 5e22, 2, 3, 0)
> > >
> > > tail-1106 [000] 113218.475673: syscall_enter: NR 2 (7fff5e42a654, 0, 0, 7fff5e429600, 80, 3)
> >
> > It's very raw indeed, but that's what Ingo asked for. :) The
> > extra args show up as whatever happened to be in those registers.
>
> If the syscalls are handled as a single tracepoint, then they
> cannot really have per syscall properties.
>
> The per syscall tracepoints on the other hand give very finegrained
> information.
>
Hi Ingo,
Aiming to identify the event payload type with the event ID alone, I
would recommend either:
- one tracepoint per syscall argument set types (e.g. same syscall
prototype)
or
- one tracepoint per syscall (seems to be more straightforward)
Otherwise getting to fit a struct sockaddr into an integer might be
cumbersome.
Thanks,
Mathieu
> Note that via the use of filters one can limit the generic
> tracepoint to only output certain syscall NRs, and only with
> certain parameters.
>
> Ingo
--
Mathieu Desnoyers
OpenPGP key fingerprint: 8CD5 52C3 8E3C 4140 715F BA06 3F25 A8FE 3BAE 9A68
next prev parent reply other threads:[~2009-08-19 13:50 UTC|newest]
Thread overview: 70+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-18 7:23 [PATCH] tracing: Move tracepoint callbacks into DEFINE Josh Stone
2009-08-18 14:19 ` Jason Baron
2009-08-18 22:11 ` Josh Stone
2009-08-18 22:25 ` [PATCH] tracing: Create generic syscall TRACE_EVENTs Josh Stone
2009-08-19 1:32 ` Li Zefan
2009-08-19 3:05 ` Josh Stone
2009-08-19 13:05 ` Ingo Molnar
2009-08-19 13:50 ` Mathieu Desnoyers [this message]
2009-08-19 16:16 ` Jason Baron
2009-08-19 17:43 ` Frederic Weisbecker
2009-08-19 16:13 ` [PATCH] tracing: Move tracepoint callbacks into DEFINE Jason Baron
2009-08-20 17:25 ` Josh Stone
2009-08-20 19:09 ` [PATCH v2 1/2] " Josh Stone
2009-08-20 19:09 ` [PATCH v2 2/2] tracing: Create generic syscall TRACE_EVENTs Josh Stone
2009-08-21 17:57 ` Jason Baron
2009-08-21 19:37 ` Josh Stone
2009-08-21 20:08 ` Jason Baron
2009-08-21 14:47 ` [PATCH v2 1/2] tracing: Move tracepoint callbacks into DEFINE Ingo Molnar
2009-08-21 19:34 ` Josh Stone
2009-08-21 17:52 ` Jason Baron
2009-08-21 19:34 ` Josh Stone
2009-08-21 20:06 ` Jason Baron
2009-08-23 20:29 ` Frederic Weisbecker
2009-08-23 20:15 ` Frederic Weisbecker
2009-08-22 4:58 ` [PATCH v3 0/4] tracing: tweaks for generic syscall events Josh Stone
2009-08-22 4:58 ` [PATCH v3 1/4] tracing: Rename TIF_SYSCALL_FTRACE->_TRACEPOINT Josh Stone
2009-08-22 4:58 ` [PATCH v3 2/4] tracing: Make syscall_(un)regfunc arch-specific Josh Stone
2009-08-22 4:58 ` [PATCH v3 3/4] tracing: Move tracepoint callbacks into DEFINE Josh Stone
2009-08-22 4:58 ` [PATCH v3 4/4] tracing: Create generic syscall TRACE_EVENTs Josh Stone
2009-08-23 21:14 ` [PATCH v3 2/4] tracing: Make syscall_(un)regfunc arch-specific Frederic Weisbecker
2009-08-24 1:40 ` Paul Mundt
2009-08-24 8:41 ` Ingo Molnar
2009-08-24 8:59 ` Paul Mundt
2009-08-24 9:56 ` Ingo Molnar
2009-08-24 10:32 ` Paul Mundt
2009-08-24 11:00 ` Ingo Molnar
2009-08-24 11:15 ` Paul Mundt
2009-08-24 11:32 ` Ingo Molnar
2009-08-24 11:52 ` Ingo Molnar
2009-08-24 12:14 ` Peter Zijlstra
2009-08-24 11:01 ` Ingo Molnar
2009-08-24 11:02 ` Paul Mundt
2009-08-24 19:31 ` Josh Stone
2009-08-24 19:58 ` Frederic Weisbecker
2009-08-24 20:00 ` Josh Stone
2009-08-24 20:12 ` Frederic Weisbecker
2009-08-23 21:16 ` [PATCH v3 1/4] tracing: Rename TIF_SYSCALL_FTRACE->_TRACEPOINT Frederic Weisbecker
2009-08-24 8:42 ` Ingo Molnar
2009-08-24 11:11 ` Frederic Weisbecker
2009-08-24 11:24 ` Ingo Molnar
2009-08-24 11:29 ` Paul Mundt
2009-08-24 11:36 ` Ingo Molnar
2009-08-24 21:43 ` [PATCH v4 0/4] tracing: tweaks for generic syscall events Josh Stone
2009-08-24 21:43 ` [PATCH v4 1/4] tracing: Rename FTRACE_SYSCALLS for tracepoints Josh Stone
2009-08-24 21:43 ` [PATCH v4 2/4] tracing: Make syscall tracepoints conditional Josh Stone
2009-08-24 21:43 ` [PATCH v4 3/4] tracing: Move tracepoint callbacks into DEFINE Josh Stone
2009-08-24 21:43 ` [PATCH v4 4/4] tracing: Create generic syscall TRACE_EVENTs Josh Stone
2009-08-26 7:22 ` [tip:tracing/core] " tip-bot for Josh Stone
2009-08-26 7:22 ` [tip:tracing/core] tracing: Move tracepoint callbacks from declaration to definition tip-bot for Josh Stone
2009-08-27 22:50 ` [PATCH] tracing: Fix double CPP substitution in TRACE_EVENT_FN Frederic Weisbecker
2009-08-28 0:38 ` Josh Stone
2009-08-28 12:29 ` [tip:tracing/core] " tip-bot for Frederic Weisbecker
2009-08-26 7:21 ` [tip:tracing/core] tracing: Make syscall tracepoints conditional tip-bot for Josh Stone
2009-08-26 7:21 ` [tip:tracing/core] tracing: Rename FTRACE_SYSCALLS for tracepoints tip-bot for Josh Stone
2009-08-24 23:05 ` [PATCH v4 0/4] tracing: tweaks for generic syscall events Frederic Weisbecker
2009-08-25 10:28 ` Ingo Molnar
2009-08-25 13:42 ` Frederic Weisbecker
2009-08-25 14:41 ` Jason Baron
2009-08-25 21:08 ` Frederic Weisbecker
2009-08-25 21:44 ` Frederic Weisbecker
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=20090819135011.GA8674@Krystal \
--to=mathieu.desnoyers@polymtl.ca \
--cc=fweisbec@gmail.com \
--cc=jbaron@redhat.com \
--cc=jiayingz@google.com \
--cc=jistone@redhat.com \
--cc=laijs@cn.fujitsu.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lizf@cn.fujitsu.com \
--cc=mbligh@google.com \
--cc=mingo@elte.hu \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.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