Linux MIPS Architecture development
 help / color / mirror / Atom feed
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: Wed, 21 Nov 2001 19:25:30 +1100	[thread overview]
Message-ID: <20011121192530.A13414@dea.linux-mips.net> (raw)
In-Reply-To: <20011121.160347.48536367.nemoto@toshiba-tops.co.jp>; from nemoto@toshiba-tops.co.jp on Wed, Nov 21, 2001 at 04:03:47PM +0900

On Wed, Nov 21, 2001 at 04:03:47PM +0900, Atsushi Nemoto wrote:

> Sometimes I want to know what kind of (and how many times) FP
> exceptions occurred in run time.  Here is a patch to provide us these
> informations via /proc/cpuinfo.
> 
> Any comments are welcome.  (This patch is not tested on SMP)

It get's atomicity wrong.  I suggest to make such statistics a per thread
thing.  That'll not only solve the SMP issues but also make sure processes
running in parallel won't influence the result.

  Ralf

  reply	other threads:[~2001-11-21  9:25 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 [this message]
2001-11-21 11:29   ` Atsushi Nemoto
2001-11-21 13:00     ` Ralf Baechle

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=20011121192530.A13414@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