From: Ralf Baechle <ralf@oss.sgi.com>
To: Atsushi Nemoto <nemoto@toshiba-tops.co.jp>
Cc: linux-mips@oss.sgi.com
Subject: Re: FP exception statistics
Date: Thu, 22 Nov 2001 00:00:40 +1100 [thread overview]
Message-ID: <20011122000040.A19180@dea.linux-mips.net> (raw)
In-Reply-To: <20011121.202906.28780735.nemoto@toshiba-tops.co.jp>; from nemoto@toshiba-tops.co.jp on Wed, Nov 21, 2001 at 08:29:06PM +0900
On Wed, Nov 21, 2001 at 08:29:06PM +0900, Atsushi Nemoto wrote:
> Yes, my patch provides "CPU" statistics (not "thread" statistics).
> Counting per thread might be useful in some case, but counting
> globally (like "unaligned_instructions" or "ll_ops" counter) is enough
> for me.
Those are certainly unlucky examples for performance counter interfaces.
We have further problems to solve in that area. Many current cpus
implement performance counters and right now Linux/MIPS doesn't use or
support those at all. Unfortunately performance counter implementations
differ wildly. We have to deciede about an interface that's supportable
by all the hardware out there.
Ralf
prev parent reply other threads:[~2001-11-21 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-21 7:03 FP exception statistics Atsushi Nemoto
2001-11-21 8:25 ` Ralf Baechle
2001-11-21 11:29 ` Atsushi Nemoto
2001-11-21 13:00 ` Ralf Baechle [this message]
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=20011122000040.A19180@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=linux-mips@oss.sgi.com \
--cc=nemoto@toshiba-tops.co.jp \
/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