From: Werner Almesberger <wa@almesberger•net>
To: benh@kernel•crashing.org
Cc: linuxppc-dev@lists•linuxppc.org
Subject: Re: performance monitor exceptions
Date: Tue, 12 Feb 2002 19:33:17 +0100 [thread overview]
Message-ID: <20020212193317.F5079@almesberger.net> (raw)
In-Reply-To: <20020212125502.32396@mailhost.mipsys.com>; from benh@kernel.crashing.org on Tue, Feb 12, 2002 at 01:55:01PM +0100
benh@kernel•crashing.org wrote:
> - I don't know how the perf. mon stuff works, but couldn't you
> enter a condition were the CPU is continuously sending your the
> pef monitor exception until you clear something else ?
No, in a performance monitor exception, PMXE (PM exception enable)
is cleared in MMCR0, and I need to set it explicitly to get another
exception. The only performance event source that's enabled is the
one using the timer base, so this gives me exceptions at 200 Hz,
more if I want.
> - I encountered a problem with the TAU stuff and the 7400 where
> the CPU could actually get mixed up when getting both a normal
> interrupt and a TAU exception and scew up itself (by taking both
> exceptions and screwing up SRR0/1)
Bingo ! That seems to be the one:
http://www.mot.co.jp/SPS/html/lit/pdf/mpc7410pns_rev0.pdf
#5:
Description: Consecutive Performance Monitor, Decrementer,
or Thermal Management Interrupts may become non-recoverable.
Work-Around: Avoid enabling any combination of
Performance Monitor, Decrementer, or Thermal Management
Interrupts at the same time.
Hmm, working around this will be tricky ...
Thanks a lot !
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Lausanne, CH wa@almesberger•net /
/_http://icawww.epfl.ch/almesberger/_____________________________________/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-02-12 18:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-11 22:37 performance monitor exceptions Werner Almesberger
2002-02-12 12:55 ` benh
2002-02-12 18:33 ` Werner Almesberger [this message]
2002-02-13 11:14 ` Anton Blanchard
2002-02-13 12:48 ` benh
2002-02-13 19:01 ` G4 boot crash problems with 2.4 "stable" David A. Gatwood
2002-02-13 19:07 ` benh
2002-02-13 21:09 ` David A. Gatwood
2002-02-13 21:06 ` Benjamin Herrenschmidt
2002-02-13 23:48 ` Ethan Benson
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=20020212193317.F5079@almesberger.net \
--to=wa@almesberger$(echo .)net \
--cc=benh@kernel$(echo .)crashing.org \
--cc=linuxppc-dev@lists$(echo .)linuxppc.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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