From: Stephane Eranian <eranian@hpl.hp.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Andrew Morton <akpm@osdl.org>,
Christoph Hellwig <hch@infradead.org>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 9/18] 2.6.17.9 perfmon2 patch for review: kernel-level interface
Date: Fri, 25 Aug 2006 00:25:01 -0700 [thread overview]
Message-ID: <20060825072501.GA5219@frankl.hpl.hp.com> (raw)
In-Reply-To: <200608250300_MC3-1-C942-6359@compuserve.com>
Hi,
On Fri, Aug 25, 2006 at 02:56:37AM -0400, Chuck Ebbert wrote:
> On Wed, 23 Aug 2006 15:54:47 -0700, Andrew Morton wrote:
>
> > > > Some users have requested the ability to create a monitoring session
> > > > with perfmon2 from iside the kernel using a kernel thread. Perfmon2
> > > > leverages a lot of kernel mechanisms which are not easy to use for
> > > > inside the kernel: e.g. file descriptor, signals, system calls.
> > >
> > > Again, please drop this. There are no planned intree kernel users
> > > so far, and once we add them we can architect a proper API for them.
> > > Getting rid of this should also help to collapse the tons of useless
> > > abstractions layers in the current perfmon code.
> > >
> >
> > Yes, I think we either need a stronger argument for including this code, or
> > we drop it.
>
> This interface is for people writing kprobes who want to do performance
> monitoring within their probe code. There will probably never be any
> in-kernel users, just like there are no in-kernel users of kprobes.
>
That is indeed the reason why I put this in. In the context of kprobes
code (callback), I don't think it is possible to make some upcall
to userland to interact with the perfmon2 interface. Yet, I think that
combining kprobes with monitoring could be very useful. A simple example
is to use kprobes to control where monitoring starts and stops, e.g.,
on a function boundaries.
> > It is especially worrisome that the exports which are added here are plain
> > old EXPORT_SYMBOL().
>
> kprobes exports are all GPL, so these should be too.
>
Yes. I am just too used to EXPORT_SYMBOL(). I will fix this in the next patch.
--
-Stephane
next prev parent reply other threads:[~2006-08-25 7:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-25 6:56 Chuck Ebbert
2006-08-25 7:25 ` Stephane Eranian [this message]
2006-08-25 13:47 ` Christoph Hellwig
2006-08-25 20:16 Chuck Ebbert
2006-08-27 18:31 ` Andi Kleen
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=20060825072501.GA5219@frankl.hpl.hp.com \
--to=eranian@hpl.hp.com \
--cc=76306.1226@compuserve.com \
--cc=akpm@osdl.org \
--cc=hch@infradead.org \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®