Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.kernel > #1594342

Re: [PATCH 1/2] x86/platform: Add a low priority low frequency NMI call chain

From Don Zickus <dzickus@redhat.com>
Newsgroups linux.kernel
Subject Re: [PATCH 1/2] x86/platform: Add a low priority low frequency NMI call chain
Date 2017-03-07 16:30 +0100
Message-ID <tipdL-11m-11@gated-at.bofh.it> (permalink)
References <ti5I7-3Hy-37@gated-at.bofh.it> <ti7gR-4VX-3@gated-at.bofh.it> <tii2B-4ft-1@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On Tue, Mar 07, 2017 at 08:42:10AM +0100, Ingo Molnar wrote:
> 
> * Mike Travis <mike.travis@hpe.com> wrote:
> 
> > Add a new NMI call chain that is called last after all other NMI handlers
> > have been checked and did not "handle" the NMI.  This mimics the current
> > NMI_UNKNOWN call chain except it eliminates the WARNING message about
> > multiple NMI handlers registering on this call chain.
> > 
> > This call chain dramatically lowers the NMI call frequency when high
> > frequency NMI tools are in use, notably the perf tools.  It is required
> > for NMI handlers that cannot sustain a high NMI call rate without
> > ramifications to the system operability.
> 
> So how about we just turn off that warning instead? I don't remember the last time 
> it actually _helped_ us find any kernel or hardware bug - and it has caused tons 
> of problems...

Yeah, that is one way to solve it. :-)

Originally I put that in there because the unknown nmi handlers sometime do
not return, making it impossible for the second handler to run.

But you are right, it probably hasn't really helped find any problems.  I
wasn't aware of problems it was causing (not that I was looking through
emails to find them either).

Cheers,
Don

> 
> It's not like we warn about excess regular IRQs either - we either handle them or 
> at most increase a counter somewhere. We could do the same for NMIs: introduce a 
> counter somewhere that counts the number of seemingly unhandled NMIs.
> 
> But in any case, we should not spam the kernel log, neither with high, nor with 
> low frequency.
> 
> Thanks,
> 
> 	Ingo

Back to linux.kernel | Previous | NextPrevious in thread | Next in thread | Find similar | Unroll thread


Thread

[PATCH 1/2] x86/platform: Add a low priority low frequency NMI call chain Mike Travis <mike.travis@hpe.com> - 2017-03-06 21:20 +0100
  Re: [PATCH 1/2] x86/platform: Add a low priority low frequency NMI  call chain Ingo Molnar <mingo@kernel.org> - 2017-03-07 08:50 +0100
    Re: [PATCH 1/2] x86/platform: Add a low priority low frequency NMI  call chain Don Zickus <dzickus@redhat.com> - 2017-03-07 16:30 +0100
      Re: [PATCH 1/2] x86/platform: Add a low priority low frequency NMI  call chain Don Zickus <dzickus@redhat.com> - 2017-03-07 17:10 +0100
    Re: [PATCH 1/2] x86/platform: Add a low priority low frequency NMI  call chain Ingo Molnar <mingo@kernel.org> - 2017-03-08 11:40 +0100
      Re: [PATCH 1/2] x86/platform: Add a low priority low frequency NMI  call chain Mike Travis <mike.travis@hpe.com> - 2017-03-08 16:20 +0100

csiph-web