From: "Frank Ch. Eigler" <fche@redhat.com>
To: Scott Dattalo <scott@dattalo.com>
Cc: sid@sources.redhat.com
Subject: Re: Profiling: --insn-count=1
Date: Thu, 01 Aug 2002 04:18:00 -0000 [thread overview]
Message-ID: <20020801071823.A7358@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.44.0207311235371.24183-100000@ruckus.brouhaha.com>; from scott@dattalo.com on Wed, Jul 31, 2002 at 12:53:37PM -0700
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
Hi, Scott -
On Wed, Jul 31, 2002 at 12:53:37PM -0700, Scott Dattalo wrote:
> [...]
> Now the question I have is there a way to count cpu cycles instead of cpu
> instructions? If there was a one-to-one relationship between the two, then
> it's not an issue. However, some instructions on the ARM are not
> single-cycled. I suppose the real question is, "is there a way to
> concisely measure the amount of 'simulated' time it take for a simulation
> to run?"
The current batch of CPU models in sid do not attempt to track the number
of cycles taken by any given instruction. To do so exactly is a crazy
amount of work to do just casually. (Think of having to model all the
pipeline interlock/bypass features, functional units.)
SID can on the other hand model memory latency, so if that's the bulk of
your interest, we can make the profile data collector sensitive to that.
> FWIW, I'm using ~6 week old copy of SID.
This hasn't changed recently.
- FChE
[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]
next prev parent reply other threads:[~2002-08-01 11:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-07-31 12:53 Scott Dattalo
2002-08-01 4:18 ` Frank Ch. Eigler [this message]
2002-08-01 5:03 ` Scott Dattalo
2002-08-01 8:32 ` Frank Ch. Eigler
2002-08-01 9:00 ` Scott Dattalo
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=20020801071823.A7358@redhat.com \
--to=fche@redhat.com \
--cc=scott@dattalo.com \
--cc=sid@sources.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).