From: bert hubert <ahu@ds9a.nl>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: linux-kernel@vger.kernel.org
Subject: Re: small perfctr bug or misunderstanding
Date: Sun, 4 Jul 2004 03:15:01 +0200 [thread overview]
Message-ID: <20040704011501.GA28252@outpost.ds9a.nl> (raw)
In-Reply-To: <200407031458.i63EwAGO023123@harpo.it.uu.se>
On Sat, Jul 03, 2004 at 04:58:10PM +0200, Mikael Pettersson wrote:
> Currently no; I removed them while we've been debating the
> API to the (IMO more important) per-process counters.
> I intend to add them back once the current stuff has been
> Linus-approved.
Ok - I'd love the ability to diagnose an entire system. Furthermore, it'd be
very cool if it were possible to profile another process, like strace -p
pid.
I think this means looking at 'virtual counters' for arbitrary processes.
Would this be possible?
I currently have a client using a 2.6.7 kernel and they have performance
problems and applications I can't recompile. It'd be very good if I could
spot which of their many application is thrashing the cache.
> The driver sees ENABLE set in EVNTSEL1 on your P-M,
> and properly returns an error.
Ahhhh, I see. With this line things work as intended:
d_control.cpu_control.evntsel[count] = v | (1 << 16) | (!count << 22) | (unit << 8);
> handle any quirks. For P6 vs K7 the differences are
> minor, but to program the P4 you _really_ need helper
> procedures.
Indeed. Thanks. I'll make a P6PerfCtr and an AMDPerfCtr and a P4PerfCtr. The
pentium 1/2 people can work it out for themselves :-)
Regards,
bert
--
http://www.PowerDNS.com Open source, database driven DNS Software
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
next prev parent reply other threads:[~2004-07-04 1:15 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-03 14:58 Mikael Pettersson
2004-07-04 1:15 ` bert hubert [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-07-03 10:28 [PATCH][2.6.7-mm5] perfctr low-level documentation Mikael Pettersson
2004-07-03 14:08 ` small perfctr bug or misunderstanding bert hubert
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=20040704011501.GA28252@outpost.ds9a.nl \
--to=ahu@ds9a.nl \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
/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
all inboxes | Powered by JetHome®