From: Will Deacon <will.deacon@arm.com>
To: kexec@lists.infradead.org
Cc: Will Deacon <will.deacon@arm.com>
Subject: [PATCH] kexec: crash: don't save swapper_pg_dir for !CONFIG_MMU configurations
Date: Fri, 24 Feb 2012 14:40:47 +0000 [thread overview]
Message-ID: <1330094447-11900-1-git-send-email-will.deacon@arm.com> (raw)
nommu platforms don't have very interesting swapper_pg_dir pointers and
usually just #define them to NULL, meaning that we can't include them in
the vmcoreinfo on the kexec crash path.
This patch only saves the swapper_pg_dir if we have an MMU.
Signed-off-by: Will Deacon <will.deacon@arm.com>
---
kernel/kexec.c | 2 ++
1 files changed, 2 insertions(+), 0 deletions(-)
diff --git a/kernel/kexec.c b/kernel/kexec.c
index 7b08867..cb5d13c 100644
--- a/kernel/kexec.c
+++ b/kernel/kexec.c
@@ -1462,7 +1462,9 @@ static int __init crash_save_vmcoreinfo_init(void)
VMCOREINFO_SYMBOL(init_uts_ns);
VMCOREINFO_SYMBOL(node_online_map);
+#ifdef CONFIG_MMU
VMCOREINFO_SYMBOL(swapper_pg_dir);
+#endif
VMCOREINFO_SYMBOL(_stext);
VMCOREINFO_SYMBOL(vmlist);
--
1.7.4.1
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
next reply other threads:[~2012-02-24 14:40 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 14:40 Will Deacon [this message]
2012-02-25 2:37 ` [PATCH] kexec: crash: don't save swapper_pg_dir for !CONFIG_MMU configurations Simon Horman
2012-02-26 22:58 ` Will Deacon
2012-02-27 0:37 ` Simon Horman
2012-02-27 19:30 ` Will Deacon
2012-02-27 23:52 ` Simon Horman
2012-02-27 23:56 ` Andrew Morton
2012-02-28 0:19 ` Simon Horman
2012-02-28 0:26 ` Andrew Morton
2012-02-28 0:51 ` Simon Horman
2012-02-28 1:25 ` Andrew Morton
2012-02-28 1:35 ` Simon Horman
2012-02-28 9:40 ` Will Deacon
2012-02-28 20:45 ` Andrew Morton
2012-02-29 1:32 ` Simon Horman
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=1330094447-11900-1-git-send-email-will.deacon@arm.com \
--to=will.deacon@arm.com \
--cc=kexec@lists.infradead.org \
/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.