[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <y0mtz7ks1jf.fsf@ton.toronto.redhat.com>
Date: Tue, 27 Jan 2009 19:43:32 -0500
From: fche@...hat.com (Frank Ch. Eigler)
To: Frederic Weisbecker <fweisbec@...il.com>
Cc: "Kok, Auke" <auke-jan.h.kok@...el.com>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
powertop ml <power@...host.org>,
Arjan van de Ven <arjan@...ux.intel.com>,
Ingo Molnar <mingo@...e.hu>, srostedt@...hat.com,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
Neil Horman <nhorman@...driver.com>, utrace-devel@...hat.com
Subject: Re: [PATCH] tracer for sys_open() - sreadahead
Frederic Weisbecker <fweisbec@...il.com> writes:
> [...]
> Speaking about a global syscall tracer, I made a patch to trace only the syscalls
> with the function-graph-tracer.
> http://lkml.org/lkml/2008/12/30/267 This low-level part can easily
> be used by all tracers that would like to inspect syscalls.
> [...]
> Just a change is needed: Steven requested that the part inside
> syscall_trace_enter become a tracepoint, making it totally shareable
> between tracers and easy to turn on and off.
Alternately, you could just rely on utrace's hooks. They were thought
out more fully with respect to parameter access, manipulation, and
programmatic control befitting even a debugger.
- FChE
--
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