From mboxrd@z Thu Jan 1 00:00:00 1970 Return-path: Received: from mtagate5.uk.ibm.com ([194.196.100.165]) by canuck.infradead.org with esmtps (Exim 4.76 #1 (Red Hat Linux)) id 1Qdmen-0001db-I2 for kexec@lists.infradead.org; Mon, 04 Jul 2011 17:10:06 +0000 Received: from d06nrmr1707.portsmouth.uk.ibm.com (d06nrmr1707.portsmouth.uk.ibm.com [9.149.39.225]) by mtagate5.uk.ibm.com (8.13.1/8.13.1) with ESMTP id p64H9uMe023423 for ; Mon, 4 Jul 2011 17:09:56 GMT Received: from d06av06.portsmouth.uk.ibm.com (d06av06.portsmouth.uk.ibm.com [9.149.37.217]) by d06nrmr1707.portsmouth.uk.ibm.com (8.13.8/8.13.8/NCO v10.0) with ESMTP id p64H9uEm1954030 for ; Mon, 4 Jul 2011 18:09:56 +0100 Received: from d06av06.portsmouth.uk.ibm.com (loopback [127.0.0.1]) by d06av06.portsmouth.uk.ibm.com (8.14.4/8.13.1/NCO v10.0 AVout) with ESMTP id p64H9tiA031589 for ; Mon, 4 Jul 2011 11:09:56 -0600 Message-Id: <20110704170959.733121710@linux.vnet.ibm.com> Date: Mon, 04 Jul 2011 19:09:29 +0200 From: Michael Holzheu Subject: [patch 7/9] kdump: Trigger kdump via panic notifier chain on s390 References: <20110704170922.976299676@linux.vnet.ibm.com> Content-Disposition: inline; filename=07-s390-kdump-common-shutdown-action.patch List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: kexec-bounces@lists.infradead.org Errors-To: kexec-bounces+dwmw2=twosheds.infradead.org@lists.infradead.org To: ebiederm@xmission.com, vgoyal@redhat.com, hbabu@us.ibm.com, mahesh@linux.vnet.ibm.com Cc: oomichi@mxs.nes.nec.co.jp, linux-s390@vger.kernel.org, kexec@lists.infradead.org, heiko.carstens@de.ibm.com, linux-kernel@vger.kernel.org, horms@verge.net.au, schwidefsky@de.ibm.com From: Michael Holzheu On s390 we have the possibility to configure actions that are executed in case of a kernel panic. E.g. it is possible to automatically trigger an s390 stand-alone dump. The actions are called via a panic notifier. We also want to trigger kdump via the notifier call chain. Therefore this patch disables for s390 the direct kdump invocation in the panic() function. Signed-off-by: Michael Holzheu --- kernel/panic.c | 3 +++ 1 file changed, 3 insertions(+) --- a/kernel/panic.c +++ b/kernel/panic.c @@ -84,9 +84,12 @@ NORET_TYPE void panic(const char * fmt, /* * If we have crashed and we have a crash kernel loaded let it handle * everything else. + * For s390 kdump is triggered via the panic notifier call chain. * Do we want to call this before we try to display a message? */ +#if !defined(CONFIG_S390) crash_kexec(NULL); +#endif kmsg_dump(KMSG_DUMP_PANIC); _______________________________________________ kexec mailing list kexec@lists.infradead.org http://lists.infradead.org/mailman/listinfo/kexec