From: Bernhard Walle <bwalle@suse.de>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: linux-arch@vger.kernel.org, discuss@x86-64.org,
kexec@lists.infradead.org, linux-kernel@vger.kernel.org,
Vivek Goyal <vgoyal@in.ibm.com>,
"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: [discuss] [patch 3/5] Use extended crashkernel command line on x86_64
Date: Sun, 9 Sep 2007 20:52:58 +0200 [thread overview]
Message-ID: <20070909185257.GA10600@suse.de> (raw)
In-Reply-To: <86802c440709091027o32a63d11w629bad87abcc19c2@mail.gmail.com>
* 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?
Thanks,
Bernhard
_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec
WARNING: multiple messages have this Message-ID (diff)
From: Bernhard Walle <bwalle@suse.de>
To: Yinghai Lu <yhlu.kernel@gmail.com>
Cc: "Eric W. Biederman" <ebiederm@xmission.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, 9 Sep 2007 20:52:58 +0200 [thread overview]
Message-ID: <20070909185257.GA10600@suse.de> (raw)
In-Reply-To: <86802c440709091027o32a63d11w629bad87abcc19c2@mail.gmail.com>
* 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?
Thanks,
Bernhard
next prev parent reply other threads:[~2007-09-09 18:53 UTC|newest]
Thread overview: 47+ 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 ` Bernhard Walle
2007-09-09 8:39 ` [patch 1/5] Extended crashkernel command line Bernhard Walle
2007-09-09 8:39 ` Bernhard Walle
2007-09-11 6:15 ` Vivek Goyal
2007-09-11 6:15 ` Vivek Goyal
2007-09-11 10:01 ` Bernhard Walle
2007-09-11 10:01 ` Bernhard Walle
2007-09-12 11:23 ` Vivek Goyal
2007-09-12 11:23 ` Vivek Goyal
2007-09-12 11:35 ` Bernhard Walle
2007-09-12 11:35 ` Bernhard Walle
2007-09-11 13:14 ` Olaf Dabrunz
2007-09-11 13:14 ` Olaf Dabrunz
2007-09-11 15:32 ` Lombard, David N
2007-09-11 15:32 ` Lombard, David N
2007-09-11 17:21 ` Bernhard Walle
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 ` Bernhard Walle
2007-09-09 8:39 ` [patch 3/5] Use extended crashkernel command line on x86_64 Bernhard Walle
2007-09-09 8:39 ` Bernhard Walle
2007-09-09 17:27 ` [discuss] " Yinghai Lu
2007-09-09 17:27 ` Yinghai Lu
2007-09-09 18:52 ` Bernhard Walle [this message]
2007-09-09 18:52 ` Bernhard Walle
2007-09-09 21:06 ` Eric W. Biederman
2007-09-09 21:06 ` Eric W. Biederman
2007-09-11 5:14 ` Vivek Goyal
2007-09-11 5:14 ` Vivek Goyal
2007-09-11 10:01 ` Bernhard Walle
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 8:39 ` Bernhard Walle
2007-09-09 8:39 ` Bernhard Walle
2007-09-09 13:01 ` Matthew Wilcox
2007-09-09 13:01 ` Matthew Wilcox
2007-09-09 13:01 ` Matthew Wilcox
2007-09-09 19:08 ` Bernhard Walle
2007-09-09 19:08 ` Bernhard Walle
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-09 8:39 ` Bernhard Walle
2007-09-11 6:09 ` [patch 0/5] Add extended crashkernel command line syntax Vivek Goyal
2007-09-11 6:09 ` Vivek Goyal
2007-09-13 15:02 ` Bernhard Walle
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=20070909185257.GA10600@suse.de \
--to=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 \
--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 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.