From: Stephane Eranian <eranian@hpl.hp.com>
To: linux-ia64@vger.kernel.org
Subject: Re: ia64 dispersal analysis capability
Date: Wed, 21 Sep 2005 18:31:30 +0000 [thread overview]
Message-ID: <20050921183130.GA13948@frankl.hpl.hp.com> (raw)
In-Reply-To: <20050921182143.GA30873@sgi.com>
On Wed, Sep 21, 2005 at 10:45:37PM -0700, David Mosberger-Tang wrote:
> On 9/21/05, Jack Steiner <steiner@sgi.com> wrote:
>
> > In 2002, Gary Hade posted a patch to binutils that added dispersal
> > analysis to the output of objdump. Does anyone know what happened to
> > the patch? Is there another tool that provides the same information?
>
> Yeah, a tool called Montecito! ;-)
>
Indeed.
> I don't remember whether you were at the last Gelato meeting and
> whether you attended the PMU talk. If you didn't: I had some slides
> in there that showed how the IP-EAR can be used to get
> instruction-group issue traces which show you exactly how many
> stall-cycles there are between subsequent instruction-groups. Yes,
> that's a bit different from the static info you are looking for, but
> in many ways it's much better info, so it's real (measured) data and
> takes into affect all corner cases, including memory latency etc.
>
You can get the presentation at:
http://www.gelato.org/pdf/may2005/gelato_may2005_profiling_eranian_callister.pdf
--
-Stephane
next prev parent reply other threads:[~2005-09-21 18:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-21 18:23 ia64 dispersal analysis capability Jack Steiner
2005-09-21 18:31 ` Stephane Eranian [this message]
2005-09-21 20:23 ` Gary Hade
2005-09-21 21:30 ` James E Wilson
2005-09-21 21:47 ` James E Wilson
2005-09-22 5:45 ` David Mosberger-Tang
2005-09-22 16:58 ` Jack Steiner
2005-09-22 17:30 ` Gary Hade
2005-09-23 20:41 ` John S. Worley
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=20050921183130.GA13948@frankl.hpl.hp.com \
--to=eranian@hpl.hp.com \
--cc=linux-ia64@vger.kernel.org \
/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