From: George Anzinger <george@mvista.com>
To: Keith Owens <kaos@sgi.com>
Cc: Andrew Morton <akpm@osdl.org>, lkml <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] NMI watch dog notify patch
Date: Thu, 28 Jul 2005 21:16:56 -0700 [thread overview]
Message-ID: <42E9ADB8.1010501@mvista.com> (raw)
In-Reply-To: <4162.1122601822@kao2.melbourne.sgi.com>
Keith Owens wrote:
> On Thu, 28 Jul 2005 13:31:58 -0700,
> George Anzinger <george@mvista.com> wrote:
>
>>I have been doing some work on kgdb to pull a few of it "fingers" out of
>>various places in the kernel. This is the final location where we have
>>a kgdb intercept not covered by a notify.
>
>
> I like the idea, but the hook should be in die_nmi(), not in the
> watchdog, using the reason that is already passed into die_nmi.
> die_nmi() is also called for a real NMI.
>
I had though that too, but it does not allow recovery (i.e. lets reset
the watchdog and try again).
Hmm.. just looked at traps.c. Seems die_nmi is NOT called from the nmi
trap, only from the watchdog. Also, there is a notify in the path to
the other nmi stuff.
--
George Anzinger george@mvista.com
HRT (High-res-timers): http://sourceforge.net/projects/high-res-timers/
next prev parent reply other threads:[~2005-07-29 4:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-28 20:31 [PATCH] NMI watch dog notify patch George Anzinger
2005-07-28 23:13 ` Andrew Morton
2005-07-28 23:58 ` George Anzinger
2005-07-29 0:12 ` Andrew Morton
2005-07-29 1:50 ` Keith Owens
2005-07-29 4:16 ` George Anzinger [this message]
2005-07-29 5:09 ` Keith Owens
2005-07-29 5:14 ` Andrew Morton
2005-07-29 20:55 ` George Anzinger
2005-07-30 3:24 ` Keith Owens
2005-08-01 22:58 ` George Anzinger
2005-08-02 20:26 ` [PATCH] " George Anzinger
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=42E9ADB8.1010501@mvista.com \
--to=george@mvista.com \
--cc=akpm@osdl.org \
--cc=kaos@sgi.com \
--cc=linux-kernel@vger.kernel.org \
/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