Content-Class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 8BIT
Subject: RE: [PATCH 2.6.x] additional kernel event notifications
Date: Sun, 21 Sep 2003 23:23:11 -0700
Message-ID: <7F740D512C7C1046AB53446D372001732DEC85@scsmsx402.sc.intel.com>
Thread-Topic: [PATCH 2.6.x] additional kernel event notifications
Thread-Index: AcN/nJ+rHa/9bFDeTzS+XSEHnxHz/wBNOomg
From: "Villacis, Juan" <juan.villacis@intel.com>
To: "Anton Blanchard" <anton@samba.org>
Cc: "Andrew Morton" <akpm@osdl.org>, <jbarnes@sgi.com>,
       <linux-kernel@vger.kernel.org>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1043
Lines: 29

Hi,

"Anton Blanchard" <anton@samba.org> writes:
> 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.

The patch we submitted adds 4 generic hooks to the existing set of
profiling hooks.  These additional hooks can be used to help performance
tools such as Oprofile and VTune to not mis-attribute performance data.

> 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.

We are open to the possibility of including the VTune driver into the
base kernel, perhaps in an architecture-dependent area.  It could
complement existing profilers.

-juan

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/