All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Blanchard <anton@samba.org>
To: "Villacis, Juan" <juan.villacis@intel.com>
Cc: Andrew Morton <akpm@osdl.org>,
	jbarnes@sgi.com, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2.6.x] additional kernel event notifications
Date: Sun, 21 Sep 2003 03:24:12 +1000	[thread overview]
Message-ID: <20030920172412.GD23414@krispykreme> (raw)
In-Reply-To: <7F740D512C7C1046AB53446D372001732DEC72@scsmsx402.sc.intel.com>


> The current event notifications used by tools like Oprofile, while quite
> useful, are not sufficient.  The additional event notifications we
> propose can provide a more complete picture for performance tuning on
> Linux, particularly for dynamically generated code (such as found in
> Java).  

Could you please explain why you cant build on top of oprofile? If arch
specific profilers start going in, we are going to have 5 different ways
of doing the same thing.

We really need to work together on this. We for example have a bunch of
ppc64 profiling stuff but throwing that into the kernel to create yet
another profiler is not the answer.

Anton

  parent reply	other threads:[~2003-09-20 17:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-19 21:18 [PATCH 2.6.x] additional kernel event notifications Villacis, Juan
2003-09-19 21:28 ` Andrew Morton
2003-09-20 17:24 ` Anton Blanchard [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-09-23  1:16 Villacis, Juan
2003-09-23 10:16 ` John Levon
2003-09-22  6:23 Villacis, Juan
2003-09-22  5:59 Villacis, Juan
2003-09-22 11:07 ` John Levon
     [not found] <xAZi.1DR.1@gated-at.bofh.it>
2003-09-20  2:02 ` Andi Kleen
2003-09-20  0:57 Villacis, Juan
2003-09-20  2:23 ` John Levon
2003-09-19 20:00 Nakajima, Jun
2003-09-19 19:32 Villacis, Juan
2003-09-19 19:35 ` Andrew Morton
2003-09-18  6:20 Villacis, Juan
2003-09-19 18:18 ` Jesse Barnes
2003-09-19 18:28   ` Andrew Morton

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=20030920172412.GD23414@krispykreme \
    --to=anton@samba.org \
    --cc=akpm@osdl.org \
    --cc=jbarnes@sgi.com \
    --cc=juan.villacis@intel.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 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.