From: Mahesh J Salgaonkar <mahesh@linux.vnet.ibm.com>
To: linuxppc-dev <linuxppc-dev@ozlabs.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Benjamin Herrenschmidt <benh@kernel.crashing.org>
Cc: Anton Blanchard <anton@samba.org>,
Amerigo Wang <amwang@redhat.com>,
Kexec-ml <kexec@lists.infradead.org>,
Milton Miller <miltonm@bga.com>,
Randy Dunlap <rdunlap@xenotime.net>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Vivek Goyal <vgoyal@redhat.com>
Subject: [RFC PATCH v6 09/10] fadump: Invalidate the fadump registration during machine shutdown.
Date: Sat, 10 Dec 2011 12:21:22 +0530 [thread overview]
Message-ID: <20111210065122.10195.980.stgit@mars.in.ibm.com> (raw)
In-Reply-To: <20111210064301.10195.3344.stgit@mars.in.ibm.com>
From: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
If dump is active during system reboot, shutdown or halt then invalidate
the fadump registration as it does not get invalidated automatically.
Signed-off-by: Mahesh Salgaonkar <mahesh@linux.vnet.ibm.com>
---
arch/powerpc/kernel/setup-common.c | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/arch/powerpc/kernel/setup-common.c b/arch/powerpc/kernel/setup-common.c
index 4e62a56..b0ebdea 100644
--- a/arch/powerpc/kernel/setup-common.c
+++ b/arch/powerpc/kernel/setup-common.c
@@ -110,6 +110,14 @@ EXPORT_SYMBOL(ppc_do_canonicalize_irqs);
/* also used by kexec */
void machine_shutdown(void)
{
+#ifdef CONFIG_FA_DUMP
+ /*
+ * if fadump is active, cleanup the fadump registration before we
+ * shutdown.
+ */
+ fadump_cleanup();
+#endif
+
if (ppc_md.machine_shutdown)
ppc_md.machine_shutdown();
}
next prev parent reply other threads:[~2011-12-10 6:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-10 6:49 [RFC PATCH v6 00/10] fadump: Firmware-assisted dump support for Powerpc Mahesh J Salgaonkar
2011-12-10 6:50 ` [RFC PATCH v6 01/10] fadump: Add documentation for firmware-assisted dump Mahesh J Salgaonkar
2011-12-10 6:50 ` [RFC PATCH v6 02/10] fadump: Reserve the memory for firmware assisted dump Mahesh J Salgaonkar
2011-12-10 6:50 ` [RFC PATCH v6 03/10] fadump: Register " Mahesh J Salgaonkar
2011-12-10 6:50 ` [RFC PATCH v6 04/10] fadump: Initialize elfcore header and add PT_LOAD program headers Mahesh J Salgaonkar
2011-12-10 6:50 ` [RFC PATCH v6 05/10] fadump: Convert firmware-assisted cpu state dump data into elf notes Mahesh J Salgaonkar
2011-12-10 6:50 ` [RFC PATCH v6 06/10] fadump: Add PT_NOTE program header for vmcoreinfo Mahesh J Salgaonkar
2011-12-10 6:51 ` [RFC PATCH v6 07/10] fadump: Introduce cleanup routine to invalidate /proc/vmcore Mahesh J Salgaonkar
2011-12-10 6:51 ` [RFC PATCH v6 08/10] fadump: Invalidate registration and release reserved memory for general use Mahesh J Salgaonkar
2011-12-10 6:51 ` Mahesh J Salgaonkar [this message]
2011-12-10 6:51 ` [RFC PATCH v6 10/10] fadump: Remove the phyp assisted dump code Mahesh J Salgaonkar
2012-02-15 4:16 ` [RFC PATCH v6 00/10] fadump: Firmware-assisted dump support for Powerpc Paul Mackerras
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=20111210065122.10195.980.stgit@mars.in.ibm.com \
--to=mahesh@linux.vnet.ibm.com \
--cc=amwang@redhat.com \
--cc=anton@samba.org \
--cc=benh@kernel.crashing.org \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linuxppc-dev@ozlabs.org \
--cc=miltonm@bga.com \
--cc=rdunlap@xenotime.net \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).