From: Thomas Horsten <thomas@horsten.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: "Steven J. Hill" <sjhill@realitydiluted.com>,
<linux-mips@linux-mips.org>
Subject: Re: [PATCH] Proposed NMI handling interface...
Date: Thu, 9 Oct 2003 13:55:12 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.40.0310091354230.16550-100000@jehova.dsm.dk> (raw)
In-Reply-To: <20031008160600.GA19102@linux-mips.org>
On Wed, 8 Oct 2003, Ralf Baechle wrote:
> That hook you're proposing isn't even necessary in generic code. NMI
> on MIPS hardware is a fairly odd type of exception - it goes straight to
> 0xbfc00000 which usually is a a firmware address - and lots of firmware
> doesn't even offer an NMI hook. So for those cases where it's possible,
> you need to do something firmware anyway before jumping to Linux's NMI
> handler. An additional problem with the NMI design of MIPS is it's using
> ErrorEPC, just like cache errors so you better pray - or simply design
> systems only to rely on NMI for debugging and catastrophic failures.
On Lasat boards NMI is used to reboot into Service Mode. There's no hook
to override this behaviour.
// Thomas
WARNING: multiple messages have this Message-ID (diff)
From: Thomas Horsten <thomas@horsten.com>
To: Ralf Baechle <ralf@linux-mips.org>
Cc: "Steven J. Hill" <sjhill@realitydiluted.com>, linux-mips@linux-mips.org
Subject: Re: [PATCH] Proposed NMI handling interface...
Date: Thu, 9 Oct 2003 13:55:12 +0100 (BST) [thread overview]
Message-ID: <Pine.LNX.4.40.0310091354230.16550-100000@jehova.dsm.dk> (raw)
Message-ID: <20031009125512.QqB41z6K5MFImG9RG84mbANnNQ5r2CyGiDhX5LBN6pw@z> (raw)
In-Reply-To: <20031008160600.GA19102@linux-mips.org>
On Wed, 8 Oct 2003, Ralf Baechle wrote:
> That hook you're proposing isn't even necessary in generic code. NMI
> on MIPS hardware is a fairly odd type of exception - it goes straight to
> 0xbfc00000 which usually is a a firmware address - and lots of firmware
> doesn't even offer an NMI hook. So for those cases where it's possible,
> you need to do something firmware anyway before jumping to Linux's NMI
> handler. An additional problem with the NMI design of MIPS is it's using
> ErrorEPC, just like cache errors so you better pray - or simply design
> systems only to rely on NMI for debugging and catastrophic failures.
On Lasat boards NMI is used to reboot into Service Mode. There's no hook
to override this behaviour.
// Thomas
next prev parent reply other threads:[~2003-10-09 12:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 20:21 [PATCH] Proposed NMI handling interface Steven J. Hill
2003-10-08 9:05 ` Maciej W. Rozycki
2003-10-08 16:06 ` Ralf Baechle
2003-10-09 12:55 ` Thomas Horsten [this message]
2003-10-09 12:55 ` Thomas Horsten
2003-10-09 16:03 ` Brian Murphy
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=Pine.LNX.4.40.0310091354230.16550-100000@jehova.dsm.dk \
--to=thomas@horsten.com \
--cc=linux-mips@linux-mips.org \
--cc=ralf@linux-mips.org \
--cc=sjhill@realitydiluted.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.