On Tue, May 01, 2018 at 06:18:44PM +0000, Joel Fernandes wrote:

quoted

quoted

From my understanding, Linux's hardlockup detector already uses the ARM

PMU

quoted

quoted

interrupt to check whether some task is stuck. I haven't looked at the
details of the implementation yet, but in theory having the PMU

interrupt as

quoted

quoted

NMI should make the hard lockup detector use the NMI.

When I do the v3, I'll have a look at this to check whether the

hardlockup

quoted

quoted

detector works fine when using NMI.

quoted

That's what I saw on arch/arm (with some of the much older FIQ work).

quoted

Once you have PMU and the appropriate config to *admit* to supporting
hard lockup then it will "just work" and be setup automatically during
kernel boot.

quoted

Actually the problem then becomes that if you want to use the PMU
for anything else then you may end up having to disable the hard
lockup detector.

This problem is not anything pseudo-NMI specific though right?
Contention/constraints on PMU resources should be a problem even on
platforms with real NMI.

Quite so. Nothing specific to pseudo-NMI; merely part of life's rich tapestry.

Moreover it is a potential surprise for anyone coming from x86 since I think
the performance monitors make it easier to run hard lockup alongside
some simple perf activity.

Either way, if you are impacted, its easy to disable the hard lockup
using procfs.


Daniel.