Re: [PATCH 2.6.x] additional kernel event notifications

[John Levon <levon@movementarian.org>]

On Fri, Sep 19, 2003 at 05:57:40PM -0700, Villacis, Juan wrote:

> both tools capture performance data, but Oprofile was designed with
> aggregation in mind whereas VTune was designed to collect all the data
> and then post-process it.

It would help a huge amount if you explained how you do :

EIP -> java source line / symbol

This is the exact transformation that oprofile *doesn't* do, and I never
managed to get a clear explanation of what you need and why for that to
happen.

In particular, your userspace must be doing some sort of communication
with the running Java VM, and the question remains open as to whether
it's possible to do that in an oprofile manner instead of a VTune 2.4 /
OProfile 2.4 manner.

I still suspect we have significant amounts of code that can be merged
between us. This would be a significant benefit to the poor saps such as
akpm who have to care about the kernel as a whole.

You also mentioned performance issues with the current OProfile code -
have we discussed the new design at all (basically: keep task structs
hanging around, remove the horrific buffer_sem)

regards
john

-- 
Khendon's Law:
If the same point is made twice by the same person, the thread is over.