public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
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>,
	Stephane Eranian <eranian@hpl.hp.com>
Subject: Re: [PATCH 9/18] 2.6.17.9 perfmon2 patch for review: kernel-level interface
Date: Fri, 25 Aug 2006 14:47:04 +0100	[thread overview]
Message-ID: <20060825134704.GA21398@infradead.org> (raw)
In-Reply-To: <200608250300_MC3-1-C942-6359@compuserve.com>

On Fri, Aug 25, 2006 at 02:56:37AM -0400, Chuck Ebbert wrote:
> > 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.

Wrong argument.  There is a in-tree user of kprobes and I plan to submit
a lot more.  If people want to write kprobes for performance mintoring
they should submit them for inclusion and we can then find a proper
API for it - the current one is rather horrible anyway.


  parent reply	other threads:[~2006-08-25 13:47 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-25  6:56 [PATCH 9/18] 2.6.17.9 perfmon2 patch for review: kernel-level interface Chuck Ebbert
2006-08-25  7:25 ` Stephane Eranian
2006-08-25 13:47 ` Christoph Hellwig [this message]
  -- strict thread matches above, loose matches on Subject: below --
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=20060825134704.GA21398@infradead.org \
    --to=hch@infradead.org \
    --cc=76306.1226@compuserve.com \
    --cc=akpm@osdl.org \
    --cc=eranian@hpl.hp.com \
    --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