[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20090129155341.GB20679@redhat.com>
Date: Thu, 29 Jan 2009 10:53:42 -0500
From: "Frank Ch. Eigler" <fche@...hat.com>
To: Frédéric Weisbecker <fweisbec@...il.com>
Cc: Ingo Molnar <mingo@...e.hu>, Roland McGrath <roland@...hat.com>,
utrace-devel@...hat.com, "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>,
Neil Horman <nhorman@...driver.com>,
Ananth N Mavinakayanahalli <ananth@...ibm.com>
Subject: Re: [PATCH] tracer for sys_open() - sreadahead
Hi -
On Thu, Jan 29, 2009 at 04:34:46PM +0100, Frédéric Weisbecker wrote:
> 2009/1/29 Ingo Molnar <mingo@...e.hu>:
> [...]
> >> > sure - how do the minimal bits/callbacks look like which enable syscall
> >> > tracing?
> I know you are talking about the only necessary bits from utrace to
> have the syscalls tracing. But I can't answer you better than would
> the utrace people. And actually I'm not sure the utrace bits for
> syscall tracing can be isolated from the rest of its core.
My understanding is that the parts of utrace that remain out-of-tree
are relatively integrated, and just present the programmatic callback
API to the already merged "tracehook" layer.
- 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