From: ebiederm@xmission.com (Eric W. Biederman)
To: Bernhard Walle <bwalle@suse.de>
Cc: Yinghai Lu <yhlu.kernel@gmail.com>,
Vivek Goyal <vgoyal@in.ibm.com>,
linux-arch@vger.kernel.org, discuss@x86-64.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [discuss] [patch 3/5] Use extended crashkernel command line on x86_64
Date: Sun, 09 Sep 2007 15:06:55 -0600 [thread overview]
Message-ID: <m1ir6jsg40.fsf@ebiederm.dsl.xmission.com> (raw)
In-Reply-To: <20070909185257.GA10600@suse.de> (Bernhard Walle's message of "Sun, 9 Sep 2007 20:52:58 +0200")
Bernhard Walle <bwalle@suse.de> writes:
> * Yinghai Lu <yhlu.kernel@gmail.com> [2007-09-09 19:27]:
>> >
>> > +#ifdef CONFIG_KEXEC
>> ...
>>
>> CONFIG_KEXEC or CONFIG_CRASH_DUMP?
>
> Good question. The crashkernel parameter was CONFIG_KEXEC before, and
> I also wondered why, but I didn't change this because maybe there's
> some reason I don't know.
>
> Vivek, do you know why this was CONFIG_KEXEC?
Probably because you use it in the primary kernel you use it.
The option reserves an area of memory for the kernel we switch
to on panic or another kernel crash.
Generally CONFIG_CRASH_DUMP seems to be about the options needed
to read out the crash dump after the fact.
Eric
next prev parent reply other threads:[~2007-09-09 21:09 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 ` [discuss] " Yinghai Lu
2007-09-09 18:52 ` Bernhard Walle
2007-09-09 21:06 ` Eric W. Biederman [this message]
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=m1ir6jsg40.fsf@ebiederm.dsl.xmission.com \
--to=ebiederm@xmission.com \
--cc=bwalle@suse.de \
--cc=discuss@x86-64.org \
--cc=kexec@lists.infradead.org \
--cc=linux-arch@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=vgoyal@in.ibm.com \
--cc=yhlu.kernel@gmail.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