From: Aristeu Rozanski <aris@redhat.com>
To: Cyrill Gorcunov <gorcunov@gmail.com>
Cc: Ingo Molnar <mingo@elte.hu>,
linux-kernel@vger.kernel.org, dzickus@redhat.com,
prarit@redhat.com, vgoyal@redhat.com
Subject: Re: [PATCH] NMI watchdog: setup before enabling NMI watchdog
Date: Mon, 22 Sep 2008 14:35:05 -0400 [thread overview]
Message-ID: <20080922183504.GN16840@redhat.com> (raw)
In-Reply-To: <20080922180535.GB22024@localhost>
> Hi Aristeu,
>
> thanks for the patch! I may be _absolutely_ wrong but could you
> explain me how we reach this site in traps
>
> ---
> if (!(reason & 0xc0)) {
> if (notify_die(DIE_NMI_IPI, "nmi_ipi", regs, reason,
> 2, SIGINT) == NOTIFY_STOP)
> return;
> /*
> * Ok, so this is none of the documented NMI sources,
> * so it must be the NMI watchdog.
> ^^^^
> */
> if (nmi_watchdog_tick(regs, reason))
> return;
> if (!do_nmi_callback(regs, cpu))
> unknown_nmi_error(reason, regs);
>
> return;
> }
> ---
>
> not having masked APIC registers as NMI entry yet (which is done during
> perfctl initialization)?
actually the comment is a bit misleading. we can get other "undocumented"
NMIs from different sources. Notice that if the nmi_watchdog_tick() doesn't
identifies it as a performance counter generated NMI (if LAPIC based, IOAPIC
always assume that the NMI is for the NMI watchdog), a default NMI callback
will be tried and if it fails, unknown_nmi_error() will be called. The first
case comes to my head is those NMI buttons present on development machines.
--
Aristeu
next prev parent reply other threads:[~2008-09-22 18:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-22 17:13 [PATCH] NMI watchdog: setup before enabling NMI watchdog Aristeu Rozanski
2008-09-22 17:47 ` Ingo Molnar
2008-09-22 17:59 ` Ingo Molnar
2008-09-22 18:12 ` Aristeu Rozanski
2008-09-22 18:05 ` Cyrill Gorcunov
2008-09-22 18:35 ` Aristeu Rozanski [this message]
2008-09-22 18:48 ` Cyrill Gorcunov
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=20080922183504.GN16840@redhat.com \
--to=aris@redhat.com \
--cc=dzickus@redhat.com \
--cc=gorcunov@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=prarit@redhat.com \
--cc=vgoyal@redhat.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.