[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <c62985530901290640j10e63127s59ce22e860a508f8@mail.gmail.com>
Date: Thu, 29 Jan 2009 15:40:55 +0100
From: Frédéric Weisbecker <fweisbec@...il.com>
To: Ingo Molnar <mingo@...e.hu>
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>,
srostedt@...hat.com,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>,
"Frank Ch. Eigler" <fche@...hat.com>,
Neil Horman <nhorman@...driver.com>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>,
utrace-devel@...hat.com, Roland McGrath <roland@...hat.com>
Subject: Re: [PATCH] tracer for sys_open() - sreadahead
2009/1/29 Ingo Molnar <mingo@...e.hu>:
>>
>> Several people talked me about utrace and gave some examples about it in
>> this discussion. The Api is very convenient to fetch syscall numbers,
>> arguments and return values. And the hooks are done in the generic core
>> code, so it is arch independent.
>>
>> The only drawback I can see is that it is not yet merged upstream, in
>> need of in-kernel users. If it only depends on this condition, we could
>> be these users...
>>
>> What do you think?
>
> sure - how do the minimal bits/callbacks look like which enable syscall
> tracing?
>
> Ingo
There is a very straightforward example provided by Ananth in there:
http://lkml.org/lkml/2009/1/28/59
--
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