From: Ralf Baechle <ralf@linux-mips.org>
To: thomas.langer@lantiq.com
Cc: markos.chandras@imgtec.com, linux-mips@linux-mips.org,
Leonid.Yegoshin@imgtec.com
Subject: Re: [PATCH] MIPS: Print correct PC in trace dump after NMI exception
Date: Tue, 8 Oct 2013 14:29:05 +0200 [thread overview]
Message-ID: <20131008122905.GJ1615@linux-mips.org> (raw)
In-Reply-To: <593AEF6C47F46446852B067021A273D6D990182F@MUCSE039.lantiq.com>
On Tue, Oct 08, 2013 at 11:48:54AM +0000, thomas.langer@lantiq.com wrote:
> > void __noreturn nmi_exception_handler(struct pt_regs *regs)
> > {
> > + char str[100];
> > +
> > raw_notifier_call_chain(&nmi_chain, 0, regs);
> > bust_spinlocks(1);
> > - printk("NMI taken!!!!\n");
> > - die("NMI", regs);
> > + snprintf(str, 100, "CPU%d NMI taken, CP0_EPC=%lx\n",
> > + smp_processor_id(), regs->cp0_epc);
> > + regs->cp0_epc = read_c0_errorepc();
>
> If this is a YAMON specific fix, why is it done in a common file?
The installation of an NMI handler is platform specific - this handler
however in all its simplicity is generic - or at least trying to.
The NMI on MIPS is notoriously hard to use. The vectors is pointing to
the boot ROM so firmware first gets its grubby hands on a fresh NMI and
on most systems it'll do the firmware equivalent of a panic or reset
the system outright. If that's still working - it's about the worst
tested functionality of firmware ...
Ralf
next prev parent reply other threads:[~2013-10-08 12:29 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-08 11:39 [PATCH] MIPS: Print correct PC in trace dump after NMI exception Markos Chandras
2013-10-08 11:39 ` Markos Chandras
2013-10-08 11:48 ` thomas.langer
2013-10-08 11:48 ` thomas.langer
2013-10-08 12:21 ` Markos Chandras
2013-10-08 12:21 ` Markos Chandras
2013-10-08 12:29 ` Ralf Baechle [this message]
2013-10-08 12:57 ` thomas.langer
2013-10-08 12:57 ` thomas.langer
2013-10-08 12:15 ` Ralf Baechle
2013-10-08 12:31 ` Markos Chandras
2013-10-08 12:31 ` Markos Chandras
2013-10-08 12:38 ` Ralf Baechle
2013-10-08 12:43 ` Markos Chandras
2013-10-08 12:43 ` Markos Chandras
2013-10-08 12:55 ` 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=20131008122905.GJ1615@linux-mips.org \
--to=ralf@linux-mips.org \
--cc=Leonid.Yegoshin@imgtec.com \
--cc=linux-mips@linux-mips.org \
--cc=markos.chandras@imgtec.com \
--cc=thomas.langer@lantiq.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