[lkml]   [2012]   [Apr]   [26]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [tip:core/locking] watchdog, hpwdt: Remove priority option for NMI callback
Hi All,

> Commit-ID: 09ee10143658cd021d879ead61ead72a196302b6
> Gitweb:
> Author: Don Zickus <>
> AuthorDate: Thu, 29 Mar 2012 16:11:15 -0400
> Committer: Ingo Molnar <>
> CommitDate: Wed, 25 Apr 2012 12:43:33 +0200
> watchdog, hpwdt: Remove priority option for NMI callback
> The NMI_UNKNOWN bucket only allows for one function to register
> to it. The reason for that is because only functions which can
> not determine if the NMI belongs to them or not should register
> and would like to assume/swallow any NMI they see.
> As a result it doesn't make sense to let more than one function
> like this register. In fact, letting a second function fail
> allows us to know that more than one function is going to
> swallow NMIs on the current system. This is better than silently
> being ignored.
> 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 <>
> Cc: Thomas Mingarelli <>
> Cc: Wim Van Sebroeck <>
> Cc: Peter Zijlstra <>
> Cc: Linus Torvalds <>
> Cc: Andrew Morton <>
> Link:
> Signed-off-by: Ingo Molnar <>

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...

Kind regards,

 \ /
  Last update: 2012-04-26 09:43    [W:0.100 / U:4.736 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site