some vtune info [wcohen@nc.rr.com: Re: VTune]

[Alexander Kellett]

here's a post to oprofile list:

note especially:
   Some features that appear to be new on this this verions of VTune:
   -No need to have a second windows machine to do the data analysis.
and:
   Their call graph code is implemented via binary rewrites and only 
   instruments basic blocks 5 bytes or large in size. So actually the call 
   graph information is finer grained than function calls. Call graph 
   information is only written out at the normal termination of a program.

Alex

----- Forwarded message from William Cohen <wcohen@nc.rr.com> -----

From: William Cohen <wcohen@nc.rr.com>
X-Accept-Language: en-us, en
To: John Levon <levon@movementarian.org>
Cc: oprofile-list@lists.sourceforge.net
Subject: Re: VTune
X-MIME-Autoconverted: from 8bit to quoted-printable by ncsmtp03.ogw.rr.com id h0GF3fj5009946
X-Original-Date: Thu, 16 Jan 2003 10:04:29 -0500

Some features that appear to be new on this this verions of VTune:

-No need to have a second windows machine to do the data analysis.
-Ability to script to do data analysis
-Ability to archive data and do data analysis on another machine

Vtune for Linux requires very specific kernels. VTune is making changes 
to the sys_call_table entries. On newer kernels Red Hat Linux kernels 
the "sys_call_table" symbol is not exported. The URL 
http://www.intel.com/software/products/vtune/vlin/relnotes.htm mentions 
that it needs to be exported for 2.4.18-17.7.xsmp. This requires a 
recompile of the code.

This VTune for Linux has a number of things that are unsupported on 
http://www.intel.com/software/products/vtune/vlin/relnotes.htm:


    *  Java* Language

    * Itanium? and Itanium? 2

    * SuSE*, Red Hat* Advanced Server* v 2.1, Red Hat* v 8.0 distributions.

    * Multiple simultaneous users (instead, the usage model is "one 
user at a time")

    * Pause/Resume APIs

    * Remote Data collection on another machine running on either a 
Linux* or Windows* operating system.


Their call graph code is implemented via binary rewrites and only 
instruments basic blocks 5 bytes or large in size. So actually the call 
graph information is finer grained than function calls. Call graph 
information is only written out at the normal termination of a program.

-Will


John Levon wrote:
>http://www.intel.com/software/products/vtune/vlin/
>
>regards
>john


----- End forwarded message -----

-- 
"[...] Konqueror open source project. Weighing in at less than
            one tenth the size of another open source renderer"
Apple,  Jan 2003 (http://www.apple.com/safari/)