From: Grant Grundler <iod00d@hp.com>
To: Chuck Ebbert <76306.1226@compuserve.com>
Cc: Stephane Eranian <eranian@hpl.hp.com>,
oprofile-list <oprofile-list@lists.sourceforge.net>,
perfmon <perfmon@napali.hpl.hp.com>,
linux-ia64 <linux-ia64@vger.kernel.org>,
perfctr-devel <perfctr-devel@lists.sourceforge.net>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.17.1 new perfmon code base, libpfm, pfmon available
Date: Mon, 26 Jun 2006 19:32:56 +0000 [thread overview]
Message-ID: <20060626193256.GE14684@esmail.cup.hp.com> (raw)
In-Reply-To: <200606261336_MC3-1-C384-7981@compuserve.com>
On Mon, Jun 26, 2006 at 01:33:03PM -0400, Chuck Ebbert wrote:
> 32-bit works great. Unfortunately, pfmon is far too limited for serious
> kernel monitoring AFAICT.
I think "far too limited for serious kernel monitoring" is not a fair
statement. One can do some very interesting things as I presented
two years ago at OLS:
http://iou.parisc-linux.org/ols_2004/pfmon_for_iodorks.pdf
It's just a _very_ complex subsystem and has a steep learning curve
to do some of the more complex things that one might like.
> E.g. you can't select edge counting instead
> of cycle counting. So you can count how many clock cycles were spent
> with interrupts disabled but you can't count how many times they were
> disabled.
At first glance, this example sounds more like a limitation of the HW
and not the SW.
> And is someone working on kernel profiling tools that use the perfmon2
> infrastructure on i386? I'd like to see kernel-based profiling that lets
> you use something like the existing 'readprofile' to retrieve results. This
> would be a lot better than the current timer-based profiling.
Both are useful. I wouldn't say one of necessarily better.
FWIW, the "CPU_CYCLES" counts from pfmon aren't timer based on ia64.
AFAIK, the HW counters are sampled to gather those counts.
thanks,
grant
next prev parent reply other threads:[~2006-06-26 19:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-21 14:24 2.6.17.1 new perfmon code base, libpfm, pfmon available Stephane Eranian
2006-06-23 21:13 ` [perfmon] " William Cohen
2006-06-23 21:23 ` [Perfctr-devel] " Stephane Eranian
2006-06-26 17:10 ` [Perfctr-devel] [perfmon] 2.6.17.1 new perfmon code base, libpfm, William Cohen
2006-06-26 17:33 ` 2.6.17.1 new perfmon code base, libpfm, pfmon available Chuck Ebbert
2006-06-26 19:32 ` Grant Grundler [this message]
2006-06-26 22:37 ` Stephane Eranian
2006-06-27 5:57 ` Chuck Ebbert
2006-06-27 14:32 ` Stephane Eranian
2006-06-27 16:51 ` Grant Grundler
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060626193256.GE14684@esmail.cup.hp.com \
--to=iod00d@hp.com \
--cc=76306.1226@compuserve.com \
--cc=eranian@hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=oprofile-list@lists.sourceforge.net \
--cc=perfctr-devel@lists.sourceforge.net \
--cc=perfmon@napali.hpl.hp.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox