All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Holzheu <holzheu@linux.vnet.ibm.com>
To: vgoyal@redhat.com
Cc: oomichi@mxs.nes.nec.co.jp, linux-s390@vger.kernel.org,
	mahesh@linux.vnet.ibm.com, heiko.carstens@de.ibm.com,
	linux-kernel@vger.kernel.org, hbabu@us.ibm.com,
	horms@verge.net.au, ebiederm@xmission.com,
	schwidefsky@de.ibm.com, kexec@lists.infradead.org
Subject: [patch v2 04/10] kdump: Trigger kdump via panic notifier chain on s390
Date: Wed, 27 Jul 2011 14:55:08 +0200	[thread overview]
Message-ID: <20110727125808.028895659@linux.vnet.ibm.com> (raw)
In-Reply-To: 20110727125504.491183728@linux.vnet.ibm.com

[-- Attachment #1: s390-kdump-common-shutdown-action.patch --]
[-- Type: text/plain, Size: 1118 bytes --]

From: Michael Holzheu <holzheu@linux.vnet.ibm.com>

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 <holzheu@linux.vnet.ibm.com>
---
 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

WARNING: multiple messages have this Message-ID (diff)
From: Michael Holzheu <holzheu@linux.vnet.ibm.com>
To: vgoyal@redhat.com
Cc: ebiederm@xmission.com, mahesh@linux.vnet.ibm.com,
	hbabu@us.ibm.com, oomichi@mxs.nes.nec.co.jp, horms@verge.net.au,
	schwidefsky@de.ibm.com, heiko.carstens@de.ibm.com,
	kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
	linux-s390@vger.kernel.org
Subject: [patch v2 04/10] kdump: Trigger kdump via panic notifier chain on s390
Date: Wed, 27 Jul 2011 14:55:08 +0200	[thread overview]
Message-ID: <20110727125808.028895659@linux.vnet.ibm.com> (raw)
In-Reply-To: 20110727125504.491183728@linux.vnet.ibm.com

[-- Attachment #1: s390-kdump-common-shutdown-action.patch --]
[-- Type: text/plain, Size: 973 bytes --]

From: Michael Holzheu <holzheu@linux.vnet.ibm.com>

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 <holzheu@linux.vnet.ibm.com>
---
 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);
 

  parent reply	other threads:[~2011-07-27 12:58 UTC|newest]

Thread overview: 66+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-27 12:55 [patch v2 00/10] kdump: Patch series for s390 support (version 2) Michael Holzheu
2011-07-27 12:55 ` Michael Holzheu
2011-07-27 12:55 ` [patch v2 01/10] kdump: Add KEXEC_CRASH_CONTROL_MEMORY_LIMIT Michael Holzheu
2011-07-27 12:55   ` Michael Holzheu
2011-08-01 20:16   ` Vivek Goyal
2011-08-01 20:16     ` Vivek Goyal
2011-08-02  9:51     ` Michael Holzheu
2011-08-02  9:51       ` Michael Holzheu
2011-08-02 19:16       ` Vivek Goyal
2011-08-02 19:16         ` Vivek Goyal
2011-08-03  9:27         ` Michael Holzheu
2011-08-03  9:27           ` Michael Holzheu
2011-07-27 12:55 ` [patch v2 02/10] kdump: Make kimage_load_crash_segment() weak Michael Holzheu
2011-07-27 12:55   ` Michael Holzheu
2011-08-01 20:31   ` Vivek Goyal
2011-08-01 20:31     ` Vivek Goyal
2011-08-02  9:30     ` Michael Holzheu
2011-08-02  9:30       ` Michael Holzheu
2011-08-02 18:55       ` Vivek Goyal
2011-08-02 18:55         ` Vivek Goyal
2011-08-03 10:41         ` Michael Holzheu
2011-08-03 10:41           ` Michael Holzheu
2011-08-04 20:25           ` Vivek Goyal
2011-08-04 20:25             ` Vivek Goyal
2011-07-27 12:55 ` [patch v2 03/10] kdump: Add size to elfcorehdr kernel parameter Michael Holzheu
2011-07-27 12:55   ` Michael Holzheu
2011-08-01 20:36   ` Vivek Goyal
2011-08-01 20:36     ` Vivek Goyal
2011-08-02  9:08     ` Michael Holzheu
2011-08-02  9:08       ` Michael Holzheu
2011-08-02 18:55       ` Vivek Goyal
2011-08-02 18:55         ` Vivek Goyal
2011-08-03 10:40         ` Michael Holzheu
2011-08-03 10:40           ` Michael Holzheu
2011-07-27 12:55 ` Michael Holzheu [this message]
2011-07-27 12:55   ` [patch v2 04/10] kdump: Trigger kdump via panic notifier chain on s390 Michael Holzheu
2011-08-01 20:41   ` Vivek Goyal
2011-08-01 20:41     ` Vivek Goyal
2011-08-02  8:37     ` Michael Holzheu
2011-08-02  8:37       ` Michael Holzheu
2011-08-02 19:21       ` Vivek Goyal
2011-08-02 19:21         ` Vivek Goyal
2011-08-03  9:50         ` Michael Holzheu
2011-08-03  9:50           ` Michael Holzheu
2011-08-04 21:14           ` Vivek Goyal
2011-08-04 21:14             ` Vivek Goyal
2011-08-08 17:47             ` Michael Holzheu
2011-08-08 17:47               ` Michael Holzheu
2011-08-09 21:19               ` Vivek Goyal
2011-08-09 21:19                 ` Vivek Goyal
2011-07-27 12:55 ` [patch v2 05/10] s390: Add PSW restart shutdown trigger Michael Holzheu
2011-07-27 12:55   ` Michael Holzheu
2011-08-01 20:54   ` Vivek Goyal
2011-08-01 20:54     ` Vivek Goyal
2011-08-02  8:05     ` Michael Holzheu
2011-08-02  8:05       ` Michael Holzheu
2011-07-27 12:55 ` [patch v2 06/10] s390: Export store_status() function Michael Holzheu
2011-07-27 12:55   ` Michael Holzheu
2011-07-27 12:55 ` [patch v2 07/10] s390: Use diagnose 308 for system reset Michael Holzheu
2011-07-27 12:55   ` Michael Holzheu
2011-07-27 12:55 ` [patch v2 08/10] s390: Add real memory access functions Michael Holzheu
2011-07-27 12:55   ` Michael Holzheu
2011-07-27 12:55 ` [patch v2 09/10] s390: kdump backend code Michael Holzheu
2011-07-27 12:55   ` Michael Holzheu
2011-07-27 12:55 ` [patch v2 10/10] kexec-tools: Add s390 kdump support Michael Holzheu
2011-07-27 12:55   ` Michael Holzheu

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110727125808.028895659@linux.vnet.ibm.com \
    --to=holzheu@linux.vnet.ibm.com \
    --cc=ebiederm@xmission.com \
    --cc=hbabu@us.ibm.com \
    --cc=heiko.carstens@de.ibm.com \
    --cc=horms@verge.net.au \
    --cc=kexec@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-s390@vger.kernel.org \
    --cc=mahesh@linux.vnet.ibm.com \
    --cc=oomichi@mxs.nes.nec.co.jp \
    --cc=schwidefsky@de.ibm.com \
    --cc=vgoyal@redhat.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.