summaryrefslogtreecommitdiffstats
path: root/scripts
diff options
context:
space:
mode:
authorLaurent Dufour <ldufour@linux.ibm.com>2022-07-13 17:47:29 +0200
committerMichael Ellerman <mpe@ellerman.id.au>2022-07-27 13:36:03 +0200
commit118b1366930c8c833b8b36abef657f40d4e26610 (patch)
tree37b9501a67eb520c09711c67e11f94b946a79bf9 /scripts
parentpowerpc/watchdog: introduce a NMI watchdog's factor (diff)
downloadlinux-118b1366930c8c833b8b36abef657f40d4e26610.tar.xz
linux-118b1366930c8c833b8b36abef657f40d4e26610.zip
powerpc/pseries/mobility: set NMI watchdog factor during an LPM
During an LPM, while the memory transfer is in progress on the arrival side, some latencies are generated when accessing not yet transferred pages on the arrival side. Thus, the NMI watchdog may be triggered too frequently, which increases the risk to hit an NMI interrupt in a bad place in the kernel, leading to a kernel panic. Disabling the Hard Lockup Watchdog until the memory transfer could be a too strong work around, some users would want this timeout to be eventually triggered if the system is hanging even during an LPM. Introduce a new sysctl variable nmi_watchdog_factor. It allows to apply a factor to the NMI watchdog timeout during an LPM. Just before the CPUs are stopped for the switchover sequence, the NMI watchdog timer is set to watchdog_thresh + factor% A value of 0 has no effect. The default value is 200, meaning that the NMI watchdog is set to 30s during LPM (based on a 10s watchdog_thresh value). Once the memory transfer is achieved, the factor is reset to 0. Setting this value to a high number is like disabling the NMI watchdog during an LPM. Signed-off-by: Laurent Dufour <ldufour@linux.ibm.com> Reviewed-by: Nicholas Piggin <npiggin@gmail.com> Signed-off-by: Michael Ellerman <mpe@ellerman.id.au> Link: https://lore.kernel.org/r/20220713154729.80789-5-ldufour@linux.ibm.com
Diffstat (limited to 'scripts')
0 files changed, 0 insertions, 0 deletions