public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andi Kleen <ak@suse.de>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Stephane Eranian <eranian@hpl.hp.com>,
	linux-kernel <linux-kernel@vger.kernel.org>,
	Andrew Morton <akpm@osdl.org>
Subject: Re: [PATCH 9/18] 2.6.17.9 perfmon2 patch for review: kernel-level interface
Date: 27 Aug 2006 20:31:09 +0200	[thread overview]
Message-ID: <p73ejv2do9e.fsf@verdi.suse.de> (raw)
In-Reply-To: <200608251618_MC3-1-C958-74D1@compuserve.com>

Chuck Ebbert <76306.1226@compuserve.com> writes:

> In-Reply-To: <20060825134704.GA21398@infradead.org>
> 
> On Fri, 25 Aug 2006 14:47:04 +0100, Christoph Hellwig wrote:
> 
> > > 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.
> 
> OK.  More than two years after kprobes went into the kernel, a single
> in-kernel user has now appeared in 2.6.18-rc: /net/ipv4/tcp_probe.c

No rules without exceptions. But there has to be a quite good rationale.
kprobes had one.  The mythical perfmon in kernel user doesn't so far.

-Andi

  reply	other threads:[~2006-08-27 18:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-25 20:16 [PATCH 9/18] 2.6.17.9 perfmon2 patch for review: kernel-level interface Chuck Ebbert
2006-08-27 18:31 ` Andi Kleen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-08-25  6:56 Chuck Ebbert
2006-08-25  7:25 ` Stephane Eranian
2006-08-25 13:47 ` Christoph Hellwig

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=p73ejv2do9e.fsf@verdi.suse.de \
    --to=ak@suse.de \
    --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