[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101213123810.GA5407@ghostprotocols.net>
Date: Mon, 13 Dec 2010 10:38:10 -0200
From: Arnaldo Carvalho de Melo <acme@...radead.org>
To: Peter Zijlstra <a.p.zijlstra@...llo.nl>
Cc: Hitoshi Mitake <mitake@....info.waseda.ac.jp>, mingo@...hat.com,
hpa@...or.com, paulus@...ba.org, linux-kernel@...r.kernel.org,
andi@...stfloor.org, yakui.zhao@...el.com, fweisbec@...il.com,
ling.ma@...el.com, rostedt@...dmis.org, miaox@...fujitsu.com,
tglx@...utronix.de, mingo@...e.hu
Subject: Re: perf monitoring triggers Was: Re: [tip:perf/core] perf bench:
Print both of prefaulted and no prefaulted results by default
Em Mon, Dec 13, 2010 at 12:14:33PM +0100, Peter Zijlstra escreveu:
> On Sun, 2010-12-12 at 11:46 -0200, Arnaldo Carvalho de Melo wrote:
> > Looks interesting, and also interesting would be to be able to place
> > probes that would wake up it too, for unmodified binaries to have
> > something similar.
> > Other kinds of triggers may be to hook on syscalls and when some
> > expression matches, like connecting to host 1.2.3.4, start monitoring,
> > stop when the socket is closed, i.e. monitor a connection lifetime, etc.
> Sounds to me like you want something like a library with self-monitoring
> stuff.
Yeah, that could be a way, an LD_PRELOAD thingy that would intercept
library calls, setup counters, start a monitoring thread, etc.
Along the lines of:
http://git.kernel.org/?p=linux/kernel/git/acme/libautocork.git;a=blob;f=libautocork.c
This one just intercepts calls, but the __init function could do the
rest.
To make it easier we could move the counter setup we have in record/top
to a library, etc.
- Arnaldo
--
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