[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090812142917.GA19882@elte.hu>
Date: Wed, 12 Aug 2009 16:29:17 +0200
From: Ingo Molnar <mingo@...e.hu>
To: Jason Baron <jbaron@...hat.com>
Cc: Frederic Weisbecker <fweisbec@...il.com>,
LKML <linux-kernel@...r.kernel.org>,
Lai Jiangshan <laijs@...fujitsu.com>,
Steven Rostedt <rostedt@...dmis.org>,
Peter Zijlstra <peterz@...radead.org>,
Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>,
Jiaying Zhang <jiayingz@...gle.com>,
Martin Bligh <mbligh@...gle.com>,
Li Zefan <lizf@...fujitsu.com>,
Masami Hiramatsu <mhiramat@...hat.com>
Subject: Re: [GIT PULL] tracing: Syscalls trace events + perf support
* Jason Baron <jbaron@...hat.com> wrote:
> On Wed, Aug 12, 2009 at 01:14:36PM +0200, Ingo Molnar wrote:
> > another thing: could we please also have a generic, highlevel
> > tracepoint (in addition to the specific tracepoints) that
> > enumerates the raw syscall Nr and the parameters it gets - in a
> > single tracepoint?
>
> The specific tracepoints, are all layered on 2 (entry, exit)
> generic tracepoints already. So this shouldn't be too hard...The
> parameters it gets might be tricky, since there are a variable
> number b/w different syscalls?
We should just list all ~6 of them. It's up to the sampling entity
to decide which ones (if any) is relevant.
At least on x86 the syscall arguments will always have a value when
the syscall entry code is called. (they are in GP registers)
Ingo
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists