From: Aristeu Rozanski <aris@ruivo.org>
To: "Maciej W. Rozycki" <macro@linux-mips.org>
Cc: Ingo Molnar <mingo@elte.hu>, Thomas Gleixner <tglx@linutronix.de>,
Vivek Goyal <vgoyal@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [RFC][PATCH] nmi watchdog: handle NMI_IO_APIC on nmi_watchdog
Date: Wed, 22 Oct 2008 23:35:40 -0400 [thread overview]
Message-ID: <20081023033540.GF28317@cathedrallabs.org> (raw)
In-Reply-To: <alpine.LFD.1.10.0810222329410.24509@ftp.linux-mips.org>
> > > but this stops all NMIs, not just the IO-APIC generated ones, doesnt it?
> > external NMIs would come by LINT1, no?
>
> Correct.
>
> > after reading a lot and talking with Vivek, what I understood was that 8259 is
> > also connected to LINT0, so timer interrupts would be reported both in
> > IOAPIC and on LINT0. LVT0 is being configured on setup_nmi() to generate
> > an NMI. Also, the same timer interrupt would generate an regular interrupt
> > coming from IOAPIC. Clearing the APIC_DM_NMI on LVT0 would disable the
> > NMI delivery, but not the regular interrupt.
> > or am I missing something here?
>
> You are correct. The routing of the 8254 timer interrupt may vary, but
> the NMI watchdog it drives, if supported, always uses the LINT0 input of
> all the local APICs.
thanks
> You seem to be writing in reply to a very old thread -- please make sure
> your concerns are still valid with current code. For example we have an
> implementation of __acpi_nmi_disable() now, which is exactly your proposed
> one.
didn't noticed that, sorry.
--
Aristeu
next prev parent reply other threads:[~2008-10-23 3:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-13 18:05 Aristeu Rozanski
2008-03-21 11:47 ` Ingo Molnar
2008-03-26 15:24 ` Aristeu Rozanski
2008-03-26 18:23 ` Ingo Molnar
2008-03-26 18:44 ` Aristeu Rozanski
2008-10-22 21:50 ` Aristeu Rozanski
2008-10-22 22:45 ` Maciej W. Rozycki
2008-10-23 3:35 ` Aristeu Rozanski [this message]
2008-10-23 21:59 ` Maciej W. Rozycki
2008-03-14 14:45 Aristeu Rozanski
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=20081023033540.GF28317@cathedrallabs.org \
--to=aris@ruivo.org \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@linux-mips.org \
--cc=mingo@elte.hu \
--cc=tglx@linutronix.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®