Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 22 Mar 2006 00:19:01 +0530
From:      "Joseph Koshy" <joseph.koshy@gmail.com>
To:        "Andrew Gallatin" <gallatin@cs.duke.edu>
Cc:        Robert Watson <rwatson@freebsd.org>, current@freebsd.org
Subject:   Re: The sixty second pmc howto
Message-ID:  <84dead720603211049o5b3a586w78d02bd1d88573b3@mail.gmail.com>
In-Reply-To: <17440.17965.497455.777452@grasshopper.cs.duke.edu>
References:  <20060223143856.O9642@fledge.watson.org> <17405.53911.686306.362353@grasshopper.cs.duke.edu> <84dead720603202346t6fe1e94cve033bf002dffa90a@mail.gmail.com> <17440.17965.497455.777452@grasshopper.cs.duke.edu>

next in thread | previous in thread | raw e-mail | index | archive | help
> For a few modules, I suppose it is OK.  But it makes it hard to
> see the "big picture" when a number of modules are loaded.
> Is there any chance you have enough information to hack
> together a view similar to oprofile's opreport -l? Or
> (even better) opreport -ld

Incidentally,

  pmcstat -R sample.out    # no '-g'

dumps a 'text' representation of the sample log that could
be parsed by an awk/perl/python script.

I've been planning a Python interface to the pmc(3) and
pmclog(3) API to aid the creation of interesting tools.
This is, as of now, only partially implemented.

--
FreeBSD Volunteer,     http://people.freebsd.org/~jkoshy



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?84dead720603211049o5b3a586w78d02bd1d88573b3>