From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932404AbbLNKWj (ORCPT ); Mon, 14 Dec 2015 05:22:39 -0500 Received: from mail.skyhub.de ([78.46.96.112]:50860 "EHLO mail.skyhub.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932140AbbLNKTV (ORCPT ); Mon, 14 Dec 2015 05:19:21 -0500 From: Borislav Petkov To: Ingo Molnar Cc: LKML Subject: [PATCH 0/7] tip-queue 2015-12-14 Date: Mon, 14 Dec 2015 11:19:08 +0100 Message-Id: <1450088355-27996-1-git-send-email-bp@alien8.de> X-Mailer: git-send-email 2.3.5 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Borislav Petkov Hi Ingo, here's a pile which addresses issues which arise when using an NMI button on certain platforms which provide it, to cause an external NMI and thus cause a concurrent kdump to fail. For that, we're getting a new cmdline option called "apic_extnmi" which can control which CPUs (or none) to receive the external NMI. The default behavior is what the kernel does currently - only the BSP receives it. I've made sure that each commit message explains in great detail what the problem is as this whole area is not trivial. Please apply, thanks. Borislav Petkov (1): x86/mm: Align macro defines Hidehiro Kawai (6): panic, x86: Fix re-entrance problem due to panic on NMI panic, x86: Allow CPUs to save registers even if looping in NMI context kexec: Fix race between panic() and crash_kexec() x86/apic: Introduce apic_extnmi command line parameter x86/nmi: Save regs in crash dump on external NMI Documentation: Document kernel.panic_on_io_nmi sysctl