From: Andrew Morton <akpm@linux-foundation.org>
To: Olaf Hering <olaf@aepfle.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] crash_dump: export is_kdump_kernel to modules, consolidate elfcorehdr_addr, setup_elfcorehdr and saved_max_pfn
Date: Thu, 27 Jan 2011 14:49:16 -0800 [thread overview]
Message-ID: <20110127144916.a311e637.akpm@linux-foundation.org> (raw)
In-Reply-To: <20110127104713.GA31360@aepfle.de>
On Thu, 27 Jan 2011 11:47:13 +0100
Olaf Hering <olaf@aepfle.de> wrote:
> On Wed, Jan 26, Andrew Morton wrote:
>
> > On Tue, 25 Jan 2011 17:10:52 +0100
> > Olaf Hering <olaf@aepfle.de> wrote:
>
> > > --- /dev/null
> > > +++ linux-2.6.38.rc/kernel/crash_dump.c
> > > @@ -0,0 +1,33 @@
> > > +#include <linux/crash_dump.h>
> > > +#include <linux/init.h>
> > > +#include <linux/module.h>
> > > +
> > > +/*
> > > + * If we have booted due to a crash, max_pfn will be a very low value. We need
> > > + * to know the amount of memory that the previous kernel used.
> > > + */
> > > +unsigned long saved_max_pfn;
> > > +
> > > +/*
> > > + * stores the physical address of elf header of crash image
> > > + *
> > > + * Note: elfcorehdr_addr is not just limited to vmcore. It is also used by
> > > + * is_kdump_kernel() to determine if we are booting after a panic. Hence put
> > > + * it under CONFIG_CRASH_DUMP and not CONFIG_PROC_VMCORE.
> > > + */
> > > +unsigned long long elfcorehdr_addr = ELFCORE_ADDR_MAX;
> > > +EXPORT_SYMBOL_GPL(elfcorehdr_addr);
> > > +
> > > +/*
> > > + * elfcorehdr= specifies the location of elf core header stored by the crashed
> > > + * kernel. This option will be passed by kexec loader to the capture kernel.
> > > + */
> > > +static int __init setup_elfcorehdr(char *arg)
> > > +{
> > > + char *end;
> > > + if (!arg)
> > > + return -EINVAL;
> > > + elfcorehdr_addr = memparse(arg, &end);
> > > + return end > arg ? 0 : -EINVAL;
> > > +}
> > > +early_param("elfcorehdr", setup_elfcorehdr);
> >
> > Please check that this file is #including everything it needs. Just
> > looking at it I'd expect a build error with CONFIG_KEXEC=n,
> > CONFIG_CRASH_DUMP=y due to a missed ELFCORE_ADDR_MAX definition.
>
> I'm not sure what you mean? ELFCORE_ADDR_MAX is in linux/crash_dump.h
> defined unconditionally. I dont see the relation to CONFIG_KEXEC.
OK, I didn't look too closely. I asked you to. memparse()? EINVAL?
--- a/kernel/crash_dump.c~crash_dump-export-is_kdump_kernel-to-modules-consolidate-elfcorehdr_addr-setup_elfcorehdr-and-saved_max_pfn-fix
+++ a/kernel/crash_dump.c
@@ -1,5 +1,7 @@
+#include <linux/kernel.h>
#include <linux/crash_dump.h>
#include <linux/init.h>
+#include <linux/errno.h>
#include <linux/module.h>
/*
_
next prev parent reply other threads:[~2011-01-27 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-25 16:10 Olaf Hering
2011-01-26 5:24 ` WANG Cong
2011-01-27 0:04 ` Andrew Morton
2011-01-27 10:47 ` Olaf Hering
2011-01-27 22:49 ` Andrew Morton [this message]
2011-01-27 2:43 ` Vivek Goyal
2011-01-27 10:57 ` Olaf Hering
2011-01-27 22:49 ` Andrew Morton
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=20110127144916.a311e637.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olaf@aepfle.de \
/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
all inboxes | Powered by JetHome®