The patch titled
x86_64: inhibit machine from asserting an NMI when doing Alt-SysRq-M operation
has been removed from the -mm tree. Its filename was
x86_64-inhibit-machine-from-asserting-an-nmi-when-doing-alt-sysrq-m-operation.patch
This patch was dropped because it was merged into mainline or a subsystem tree
------------------------------------------------------
Subject: x86_64: inhibit machine from asserting an NMI when doing Alt-SysRq-M operation
From: Konrad Rzeszutek <konrad@xxxxxxxxxx>
Touch the NMI watchdog to inhibit the machine from triggering an NMI while
the CPUs are locked. This situation is happening on boxes with more than
64CPUs and 128GB of RAM when Alt-SysRq-m is performed.
It has been succesfully tested for regression on uni, 2, 4, 8 32, and 64
CPU boxes with various memory configuration.
Cc: Andi Kleen <ak@xxxxxxx>
Signed-off-by: Andrew Morton <akpm@xxxxxxxxxxxxxxxxxxxx>
---
arch/x86_64/mm/init.c | 6 ++++++
1 files changed, 6 insertions(+)
diff -puN arch/x86_64/mm/init.c~x86_64-inhibit-machine-from-asserting-an-nmi-when-doing-alt-sysrq-m-operation arch/x86_64/mm/init.c
--- a/arch/x86_64/mm/init.c~x86_64-inhibit-machine-from-asserting-an-nmi-when-doing-alt-sysrq-m-operation
+++ a/arch/x86_64/mm/init.c
@@ -26,6 +26,7 @@
#include <linux/dma-mapping.h>
#include <linux/module.h>
#include <linux/memory_hotplug.h>
+#include <linux/nmi.h>
#include <asm/processor.h>
#include <asm/system.h>
@@ -72,6 +73,11 @@ void show_mem(void)
for_each_online_pgdat(pgdat) {
for (i = 0; i < pgdat->node_spanned_pages; ++i) {
+ /* this loop can take a while with 256 GB and 4k pages
+ so update the NMI watchdog */
+ if (unlikely(i % MAX_ORDER_NR_PAGES == 0)) {
+ touch_nmi_watchdog();
+ }
page = pfn_to_page(pgdat->node_start_pfn + i);
total++;
if (PageReserved(page))
_
Patches currently in -mm which might be from konrad@xxxxxxxxxx are
x86_64-inhibit-machine-from-asserting-an-nmi-when-doing-alt-sysrq-m-operation-tidy.patch
-
To unsubscribe from this list: send the line "unsubscribe mm-commits" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
