From: Don Zickus <dzickus@redhat.com>
To: Wim Van Sebroeck <wim@iguana.be>
Cc: mingo@kernel.org, hpa@zytor.com, linux-kernel@vger.kernel.org,
torvalds@linux-foundation.org, peterz@infradead.org,
thomas.mingarelli@hp.com, akpm@linux-foundation.org,
tglx@linutronix.de, linux-tip-commits@vger.kernel.org
Subject: Re: [tip:core/locking] watchdog, hpwdt: Remove priority option for NMI callback
Date: Thu, 26 Apr 2012 08:26:59 -0400 [thread overview]
Message-ID: <20120426122659.GS28185@redhat.com> (raw)
In-Reply-To: <20120426071339.GI6553@spo001.leaseweb.com>
On Thu, Apr 26, 2012 at 09:13:39AM +0200, Wim Van Sebroeck wrote:
> >
> > Therefore hpwdt's priority mechanism doesn't make sense any
> > more. They will be always first on the NMI_UNKNOWN queue, if
> > they register.
> >
> > Removing this parameter cleans up the code and simplifies things
> > for the next patch which changes how nmis are registered.
> >
> > Signed-off-by: Don Zickus <dzickus@redhat.com>
> > Cc: Thomas Mingarelli <thomas.mingarelli@hp.com>
> > Cc: Wim Van Sebroeck <wim@iguana.be>
> > Cc: Peter Zijlstra <peterz@infradead.org>
> > Cc: Linus Torvalds <torvalds@linux-foundation.org>
> > Cc: Andrew Morton <akpm@linux-foundation.org>
> > Link: http://lkml.kernel.org/r/1333051877-15755-2-git-send-email-dzickus@redhat.com
> > Signed-off-by: Ingo Molnar <mingo@kernel.org>
>
> This is the feedback I have from Tom which he discussed with Don:
> > I don't like this patch because the Virtual NMI button doesn't come through the pretimeout routine. It is taken by the
> system as an IOCK NMI error and no log messages in our IML.
> > Our BIOS is not able to source the NMI.
>
> And since then it became quiet. Imho: this needs more discussion...
Tom and I discussed this offline. The result was patch 2 of this series.
The problem he had, had nothing to do with this patch (which was just a
cleanup really). Tom tested the second patch and was happy with the
results.
If there is any other issues, I am assuming Tom would have let me know a
while ago. But I believe all his issues are addressed. Tom?
Cheers,
Don
next prev parent reply other threads:[~2012-04-26 12:27 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-29 20:11 [PATCH 0/3] x86, nmi: Fixes Don Zickus
2012-03-29 20:11 ` [PATCH 1/3] watchdog, hpwdt: Remove priority option for NMI callback Don Zickus
2012-04-25 13:54 ` [tip:core/locking] " tip-bot for Don Zickus
2012-04-26 7:13 ` Wim Van Sebroeck
2012-04-26 12:26 ` Don Zickus [this message]
2012-04-26 13:47 ` Mingarelli, Thomas
2012-04-26 13:53 ` Wim Van Sebroeck
2012-03-29 20:11 ` [PATCH 2/3] x86, nmi: Add new NMI queues to deal with IO_CHK and SERR Don Zickus
2012-04-25 13:55 ` [tip:core/locking] x86/nmi: " tip-bot for Don Zickus
2012-03-29 20:11 ` [PATCH 3/3] x86,nmi: Fix page faults by nmiaction if kmemcheck is enabled Don Zickus
2012-04-25 13:55 ` [tip:core/locking] x86/nmi: " tip-bot for Li Zhong
2012-04-20 16:17 ` [PATCH 0/3] x86, nmi: Fixes Seiji Aguchi
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=20120426122659.GS28185@redhat.com \
--to=dzickus@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=hpa@zytor.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mingo@kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=thomas.mingarelli@hp.com \
--cc=torvalds@linux-foundation.org \
--cc=wim@iguana.be \
/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