Re: [PerfSuite-users] Problem with psconfig, workaround for building a config file?

[<ol...@ec...>]

Hey no problem, I appreciate your willingness to help. Well I managed to make 
some good progress and I got tDOM installed correctly. In fact, tDOM was 
installed correctly the entire time but I had set the --with-tdom=TDOM_PATH 
option in ./configure incorrectly which was causing PerfSuite to not find the 
files it needed.

psrun does work fine with profil.xml, but it doesn't report anything useful. 
The only thing it tells us is the processor, it's cache configuration, etc. 
and nothing about instruction counts, cache miss rates, or other profiling 
information. Anyway with tDOM installed correctly I enthusiasticly went to run 
psconfig to create our own configuration, when it spit out an error message:

> ERROR: Unable to find PAPI

Which I thought was completely optional. But I installed PAPI on my machine 
anyway (without patching the kernel, because I don't have the priveledges to 
do so) and re-configured and installed PerfSuite with the --with-papi=PAPI_DIR 
option, but it still did not work.

Anyway for the time being this project is being due to being a busy grad-
student, but I'll probably pick it back up sometime this summer when I have 
more free-time. In regards for making distrobution specific packages (RPMs, 
DEB, etc) I'd love to see that happen. I know on SourceForge you can place 
help wanted ads (look in the Admin section and it should be there somewher) 
and see if there are any OSS developers who can help you package it. (I'm 
assuming you don't have the time to do it yourself). I'd like to help, but I'm 
far too busy right now and I've never created packages for any of the programs 
I've written, although I'll need to learn how to soon for another OSS project 
I've been working on for over 9 months. :)

Thanks once again for all your help.


- Tyler


Quoting Rick Kufrin <rk...@nc...>:

> Tyler,
> 
> First of all, apologies for delay in my reply.  I'm currently on travel
> and not able to read or respond as quickly as I'd prefer, so thanks
> for your patience.
> 
> It's possible that there are a couple of things going on here, or rather
> *not* going on.  It does seem as if tDOM is a roadblock from what you
> report.  An improper tDOM install will prevent psprocess (or psconfig,
> as you note from your original message) from being able to work with
> either the input (XML config) or output (perf measurement) documents
> for psrun.
> 
> Although I'm not certain, it seems as though the "profil.xml" file as you 
> show does not result in a psrun runtime error, although all others do, 
> since they rely on PAPI.  If you receive an XML output file when using 
> profil.xml and psrun on your program, then that likely means that psrun
> itself is OK - the output document should contain profiling samples if
> so.  Unfortunately, psprocess (and therefore tDOM) would be required
> to map the samples in the XML doc to source code lines for the output
> to be of much use.
> 
> Can you verify that XML is output when you run psrun with the profil.xml 
> config?
> 
> If the psrun/profil.xml combination does produce output, then I think
> that points again to tDOM being the missing part in your install.
> I'd be happy to help you with the tDOM build, probably off-list is
> best.  Let me know if that might help (I am still on travel, although
> will check more frequently).
> 
> I have thought recently that providing RPMs for x86/x86-64/ia64 tDOM
> might make it easier for people to install and use PerfSuite and avoid
> this type of problem, any feedback is welcome.
> 
> Rick
> 
> On Tue, 12 Apr 2005 ol...@ec... wrote:
> 
> > Thanks for replying. Unfortunately I have already tried what you mentioned
> and
> > had no luck. First of all, the "profil.xml" file contains the following:
> > 
> > <?xml version="1.0" encoding="UTF-8" ?>
> > <ps_hwpc_profile class="null">
> >   <!-- ==========================================================
> >        This is a configuration file that can be used to ask for
> >        profiling, based on profil().
> > 
> >        $Id: profil.xml,v 1.3 2003/12/27 14:23:51 rkufrin Exp $
> >        ========================================================== -->
> > </ps_hwpc_profile>
> > 
> > 
> > It is exactly the same as the "null.xml" file (using Perfsuite-0.6.1 by
> the
> > way). And if we try to use any of the other config files (all prefixed
> with
> > papi) psrun will refuse to execute because the kernel we are running does
> not
> > have PAPI patched to it.
> > 
> > 
> > So really, we are in a situation where we have no valid config files to 
use
> and
> > are unable to build our own config files. I've spent nearly 2 days trying
> to
> > build tDOM and I have read all the documentation provided with it, but no
> matter
> > what I've tried it still builds incorrectly. If there are any other
> general
> > config files that may be laying around somewhere (especially for Xeon) 
that
> do
> > *not* use PAPI or a guide somewhere to explain the format of the config
> file so
> > we could build one by hand, it would really help us out. Thanks once
> again.
> > 
> > 
> > - Tyler
> 
> 
> 
> -------------------------------------------------------
> SF email is sponsored by - The IT Product Guide
> Read honest & candid reviews on hundreds of IT Products from real users.
> Discover which products truly live up to the hype. Start reading now.
> http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
> _______________________________________________
> PerfSuite-users mailing list
> Per...@li...
> https://lists.sourceforge.net/lists/listinfo/perfsuite-users
> 



-------------------------------------------------
This mail sent through IMP: http://horde.org/imp/