public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Cyrill Gorcunov <gorcunov@gmail.com>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
	"H. Peter Anvin" <hpa@zytor.com>,
	LKML <linux-kernel@vger.kernel.org>
Subject: Re: nmi_watchdog suspicious
Date: Sat, 21 Jun 2008 12:04:40 +0400	[thread overview]
Message-ID: <20080621080440.GA7056@cvg> (raw)
In-Reply-To: <Pine.LNX.4.55.0806210250210.19614@cliff.in.clinika.pl>

[Maciej W. Rozycki - Sat, Jun 21, 2008 at 02:54:38AM +0100]
| On Wed, 18 Jun 2008, Cyrill Gorcunov wrote:
| 
| > If you mean the case we get NMI physical line assetred while configuring APIC
| > (ie nmi watchdog is not properly configured yet) then I wonder why we has
| > this checking at all...
| 
|  Hmm, I am not sure what you mean -- nmi_watchdog_tick() can be called
| potentially at any time, and you can receive NMIs from sources other than
| the watchdog; the latters would set bits in the Port B at 0x61 in most
| cases though.  Anyway using a separate variable such as
| "nmi_watchdog_active" would be cleaner.
| 
|   Maciej
| 

ok, thanks Maciej, i'll take a look on this.

		- Cyrill -

      reply	other threads:[~2008-06-21  8:05 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-10 18:57 nmi_watchdog suspicious Cyrill Gorcunov
2008-06-10 19:10 ` Cyrill Gorcunov
2008-06-15 23:49 ` Maciej W. Rozycki
2008-06-16 17:00   ` Cyrill Gorcunov
2008-06-16 23:20     ` Maciej W. Rozycki
2008-06-17 15:51       ` Cyrill Gorcunov
2008-06-18 16:06         ` Maciej W. Rozycki
2008-06-18 16:39           ` Cyrill Gorcunov
2008-06-18 16:54             ` Maciej W. Rozycki
2008-06-18 17:23               ` Cyrill Gorcunov
2008-06-21  1:54                 ` Maciej W. Rozycki
2008-06-21  8:04                   ` Cyrill Gorcunov [this message]

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=20080621080440.GA7056@cvg \
    --to=gorcunov@gmail.com \
    --cc=hpa@zytor.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@linux-mips.org \
    --cc=mingo@elte.hu \
    --cc=tglx@linutronix.de \
    /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