From: "Frank Ch. Eigler" <fche@redhat.com>
To: "Frédéric Weisbecker" <fweisbec@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>, Roland McGrath <roland@redhat.com>,
utrace-devel@redhat.com, "Kok, Auke" <auke-jan.h.kok@intel.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
powertop ml <power@bughost.org>,
Arjan van de Ven <arjan@linux.intel.com>,
srostedt@redhat.com,
Arnaldo Carvalho de Melo <acme@ghostprotocols.net>,
Neil Horman <nhorman@tuxdriver.com>,
Ananth N Mavinakayanahalli <ananth@in.ibm.com>
Subject: Re: [PATCH] tracer for sys_open() - sreadahead
Date: Thu, 29 Jan 2009 10:53:42 -0500 [thread overview]
Message-ID: <20090129155341.GB20679@redhat.com> (raw)
In-Reply-To: <c62985530901290734i26c5b664m2b0342b29cc95807@mail.gmail.com>
Hi -
On Thu, Jan 29, 2009 at 04:34:46PM +0100, Frédéric Weisbecker wrote:
> 2009/1/29 Ingo Molnar <mingo@elte.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
next prev parent reply other threads:[~2009-01-29 15:54 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 20:08 [PATCH] tracer for sys_open() - sreadahead Kok, Auke
2009-01-27 20:51 ` Arnaldo Carvalho de Melo
2009-01-27 21:14 ` Frederic Weisbecker
2009-01-28 22:05 ` Kok, Auke
2009-01-29 0:45 ` Arnaldo Carvalho de Melo
2009-01-29 13:39 ` Frédéric Weisbecker
2009-01-29 13:40 ` Frédéric Weisbecker
2009-01-27 22:43 ` Frederic Weisbecker
2009-01-27 22:50 ` Frederic Weisbecker
2009-01-29 14:04 ` Ingo Molnar
2009-01-29 14:29 ` Frédéric Weisbecker
2009-01-29 14:31 ` Ingo Molnar
2009-01-29 14:40 ` Frédéric Weisbecker
2009-01-29 14:48 ` Frédéric Weisbecker
2009-01-29 15:09 ` Ingo Molnar
2009-01-29 15:17 ` Frédéric Weisbecker
2009-01-29 15:34 ` Frédéric Weisbecker
2009-01-29 15:53 ` Frank Ch. Eigler [this message]
2009-01-28 0:43 ` Frank Ch. Eigler
2009-01-28 13:58 ` Frédéric Weisbecker
2009-01-28 14:29 ` Arnaldo Carvalho de Melo
2009-01-28 9:38 ` Ananth N Mavinakayanahalli
2009-01-28 14:21 ` Frédéric Weisbecker
2009-01-28 17:00 ` Ananth N Mavinakayanahalli
2009-01-28 17:15 ` Frédéric Weisbecker
2009-01-28 22:19 ` Kok, Auke
2009-01-30 20:22 ` Pavel Machek
2009-02-03 13:32 ` Ingo Molnar
2009-02-05 14:44 ` Harald Hoyer
2009-02-05 15:07 ` Bill Nottingham
2009-02-05 15:14 ` Arjan van de Ven
2009-02-05 15:24 ` Bill Nottingham
2009-02-05 15:47 ` Arjan van de Ven
2009-02-06 23:18 ` Corrado Zoccolo
2009-02-09 13:13 ` Karel Zak
2009-02-09 13:23 ` Harald Hoyer
2009-02-09 13:54 ` Karel Zak
2009-02-11 10:44 ` Harald Hoyer
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=20090129155341.GB20679@redhat.com \
--to=fche@redhat.com \
--cc=acme@ghostprotocols.net \
--cc=ananth@in.ibm.com \
--cc=arjan@linux.intel.com \
--cc=auke-jan.h.kok@intel.com \
--cc=fweisbec@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=nhorman@tuxdriver.com \
--cc=power@bughost.org \
--cc=roland@redhat.com \
--cc=srostedt@redhat.com \
--cc=utrace-devel@redhat.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.