From: "Bill Rugolsky Jr." <brugolsky@telemetry-investments.com>
To: William Cohen <wcohen@redhat.com>
Cc: "Frank Ch. Eigler" <fche@redhat.com>, systemtap@sources.redhat.com
Subject: Re: Proposed systemtap access to perfmon hardware
Date: Fri, 17 Mar 2006 17:10:00 -0000 [thread overview]
Message-ID: <20060317171053.GA31131@ti64.telemetry-investments.com> (raw)
In-Reply-To: <441AE1DE.2040207@redhat.com>
On Fri, Mar 17, 2006 at 11:20:46AM -0500, William Cohen wrote:
> To try to get a feel on how the performance monitoring hardware support
> would work in SystemTap I wrote some simple examples. Below are examples
> for computing IPC, average cycle count, and sampling within a function.
> The IPC and average cycle count function need a bit of rework to work
> for a SMP machines.
>
> Let me know if there are comments or questions on the examples.
A non-statistical application for systemtap perfctrs:
In light of a suggestion made by Alan Cox yesterday,
http://lkml.org/lkml/2006/3/16/118
I'm hacking up some additions to Ingo Molnar's latency tracing patch
that will track retired insns as well as clock cycles, so I can see
where the processor is stalled on I/O, SMM traps, etc., within a given
execution path.
For the particular case that triggered the aforementioned thread, I know
the precise offending instruction, but in the general case a search
for the culprit might be necessary, and doing this with systemtap would
be convenient.
Regards,
Bill Rugolsky
next prev parent reply other threads:[~2006-03-17 17:10 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-15 16:24 William Cohen
2006-03-15 22:34 ` Frank Ch. Eigler
2006-03-17 16:20 ` William Cohen
2006-03-17 17:10 ` Bill Rugolsky Jr. [this message]
2006-03-17 17:34 ` Frank Ch. Eigler
2006-03-17 20:26 ` William Cohen
2006-03-20 17:27 ` Frank Ch. Eigler
2006-03-22 3:34 ` Maynard Johnson
2006-03-22 18:02 ` William Cohen
2006-03-22 22:16 ` Maynard Johnson
2006-03-22 18:30 ` Frank Ch. Eigler
2006-03-22 19:09 Stone, Joshua I
2006-03-22 20:04 ` Frank Ch. Eigler
2006-03-22 23:23 Stone, Joshua I
2006-03-22 23:46 Stone, Joshua I
2006-03-23 12:54 ` Maynard Johnson
2006-03-23 14:46 ` William Cohen
2006-03-23 17:09 Stone, Joshua I
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=20060317171053.GA31131@ti64.telemetry-investments.com \
--to=brugolsky@telemetry-investments.com \
--cc=fche@redhat.com \
--cc=systemtap@sources.redhat.com \
--cc=wcohen@redhat.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).