From: "Yinghai Lu" <yhlu.kernel@gmail.com>
To: Bernhard Walle <bwalle@suse.de>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Vivek Goyal <vgoyal@in.ibm.com>
Cc: kexec@lists.infradead.org, linux-arch@vger.kernel.org,
discuss@x86-64.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] [patch 3/5] Use extended crashkernel command line on x86_64
Date: Sun, 9 Sep 2007 10:27:19 -0700 [thread overview]
Message-ID: <86802c440709091027o32a63d11w629bad87abcc19c2@mail.gmail.com> (raw)
In-Reply-To: <20070909083914.951336895@strauss.suse.de>
On 9/9/07, Bernhard Walle <bwalle@suse.de> wrote:
> This patch removes the crashkernel parsing from
> arch/x86_64/kernel/machine_kexec.c and calls the generic function, introduced in
> the last patch, in setup_bootmem_allocator().
>
> This is necessary because the amount of System RAM must be known in this
> function now because of the new syntax.
>
>
> Signed-off-by: Bernhard Walle <bwalle@suse.de>
>
>
> ---
> arch/x86_64/kernel/e820.c | 3 ++-
> arch/x86_64/kernel/machine_kexec.c | 27 ---------------------------
> arch/x86_64/kernel/setup.c | 35 ++++++++++++++++++++++++++++-------
> 3 files changed, 30 insertions(+), 35 deletions(-)
>
> --- a/arch/x86_64/kernel/e820.c
> +++ b/arch/x86_64/kernel/e820.c
> @@ -226,7 +226,8 @@ void __init e820_reserve_resources(void)
> request_resource(res, &code_resource);
> request_resource(res, &data_resource);
> #ifdef CONFIG_KEXEC
...
> --- a/arch/x86_64/kernel/machine_kexec.c
> +++ b/arch/x86_64/kernel/machine_kexec.c
> @@ -231,33 +231,6 @@ NORET_TYPE void machine_kexec(struct kim
> image->start);
> }
>
> -/* crashkernel=size@addr specifies the location to reserve for
> - * a crash kernel. By reserving this memory we guarantee
> - * that linux never set's it up as a DMA target.
> - * Useful for holding code to do something appropriate
> - * after a kernel panic.
> - */
> -static int __init setup_crashkernel(char *arg)
> -{
> - unsigned long size, base;
> - char *p;
> - if (!arg)
> - return -EINVAL;
> - size = memparse(arg, &p);
> - if (arg == p)
> - return -EINVAL;
> - if (*p == '@') {
> - base = memparse(p+1, &p);
> - /* FIXME: Do I want a sanity check to validate the
> - * memory range? Yes you do, but it's too early for
> - * e820 -AK */
> - crashk_res.start = base;
> - crashk_res.end = base + size - 1;
> - }
> - return 0;
> -}
> -early_param("crashkernel", setup_crashkernel);
> -
> void arch_crash_save_vmcoreinfo(void)
> {
> #ifdef CONFIG_ARCH_DISCONTIGMEM_ENABLE
> --- a/arch/x86_64/kernel/setup.c
> +++ b/arch/x86_64/kernel/setup.c
> @@ -196,6 +196,33 @@ static inline void copy_edd(void)
> }
> #endif
>
> +#ifdef CONFIG_KEXEC
...
CONFIG_KEXEC or CONFIG_CRASH_DUMP?
YH
next prev parent reply other threads:[~2007-09-09 17:27 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-09 8:39 [patch 0/5] Add extended crashkernel command line syntax Bernhard Walle
2007-09-09 8:39 ` [patch 1/5] Extended crashkernel command line Bernhard Walle
2007-09-11 6:15 ` Vivek Goyal
2007-09-11 10:01 ` Bernhard Walle
2007-09-12 11:23 ` Vivek Goyal
2007-09-12 11:35 ` Bernhard Walle
2007-09-11 13:14 ` Olaf Dabrunz
2007-09-11 15:32 ` Lombard, David N
2007-09-11 17:21 ` Bernhard Walle
2007-09-09 8:39 ` [patch 2/5] Use extended crashkernel command line on i386 Bernhard Walle
2007-09-09 8:39 ` [patch 3/5] Use extended crashkernel command line on x86_64 Bernhard Walle
2007-09-09 17:27 ` Yinghai Lu [this message]
2007-09-09 18:52 ` [discuss] " Bernhard Walle
2007-09-09 21:06 ` Eric W. Biederman
2007-09-11 5:14 ` Vivek Goyal
2007-09-11 10:01 ` Bernhard Walle
2007-09-09 8:39 ` [patch 4/5] Use extended crashkernel command line on IA64 Bernhard Walle
2007-09-09 13:01 ` Matthew Wilcox
2007-09-09 19:08 ` Bernhard Walle
2007-09-09 8:39 ` [patch 5/5] Add documentation for extended crashkernel syntax Bernhard Walle
2007-09-11 6:09 ` [patch 0/5] Add extended crashkernel command line syntax Vivek Goyal
2007-09-13 15:02 ` Bernhard Walle
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=86802c440709091027o32a63d11w629bad87abcc19c2@mail.gmail.com \
--to=yhlu.kernel@gmail.com \
--cc=bwalle@suse.de \
--cc=discuss@x86-64.org \
--cc=ebiederm@xmission.com \
--cc=kexec@lists.infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.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).