From: linas@austin.ibm.com (Linas Vepstas)
To: Andrew Morton <akpm@linux-foundation.org>
Cc: Maxim Uvarov <muvarov@ru.mvista.com>,
dada1@cosmosbay.com, pavel@ucw.cz, wli@holomorphy.com,
linuxppc-dev@ozlabs.org
Subject: Using kprobes [was Re: [PATCH] Performance Stats: Kernel patch
Date: Fri, 11 May 2007 12:23:04 -0500 [thread overview]
Message-ID: <20070511172304.GI4452@austin.ibm.com> (raw)
In-Reply-To: <20070510111242.dd42adae.akpm@linux-foundation.org>
On Thu, May 10, 2007 at 11:12:42AM -0700, Andrew Morton wrote:
>
> I don't think the syscall-counting feature has a future, sorry. Perhaps
> you could do something like hooking it up on-demand by insertion of a kprobe,
> dunno.
This is an interesting point. I've started fiddling with (a wrapper
around) kprobes that allows me to pick any subroutine symbol in System.map,
and then get an event whenever that subroutine gets called. Its pretty
slick, and allows me to gather data on certain unusual events in the
kernel. (I'm not using this for performance monitoring, I'm trying to
do RAS).
It makes a lot of sense to me to have a generic kprobe extension, where
you could give it a list of subroutine names, and it'll collect stats
on the number of times that the routine was called. Some user-space thingy
could poll for those stats, or you could put them in /sys or wherever.
Its more complicted than just instriumenting syscalls, but a lot more
useful, I would think ...
--linas
next prev parent reply other threads:[~2007-05-11 17:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 16:26 [PATCH] Performance Stats: Kernel patch Maxim Uvarov
2007-05-08 19:32 ` Andrew Morton
2007-05-10 11:11 ` Maxim Uvarov
2007-05-10 18:12 ` Andrew Morton
2007-05-11 16:51 ` Maxim Uvarov
2007-05-11 17:23 ` Linas Vepstas [this message]
2007-05-12 9:15 ` Using kprobes [was " Christoph Hellwig
2007-05-21 15:28 ` Maxim Uvarov
2007-05-08 23:32 ` Linas Vepstas
2007-05-10 10:22 ` Maxim Uvarov
2007-05-10 16:47 ` Linas Vepstas
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=20070511172304.GI4452@austin.ibm.com \
--to=linas@austin.ibm.com \
--cc=akpm@linux-foundation.org \
--cc=dada1@cosmosbay.com \
--cc=linuxppc-dev@ozlabs.org \
--cc=muvarov@ru.mvista.com \
--cc=pavel@ucw.cz \
--cc=wli@holomorphy.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.