public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vivek Goyal <vgoyal@in.ibm.com>
To: Adrian Bunk <bunk@stusta.de>
Cc: linux-kernel@vger.kernel.org,
	Fastboot mailing list <fastboot@lists.osdl.org>,
	"Eric W. Biederman" <ebiederm@xmission.com>
Subject: Re: strange CRASH_DUMP dependencies
Date: Tue, 23 Aug 2005 12:44:47 +0530	[thread overview]
Message-ID: <20050823071447.GB3766@in.ibm.com> (raw)
In-Reply-To: <20050822204417.GI9927@stusta.de>

On Mon, Aug 22, 2005 at 10:44:17PM +0200, Adrian Bunk wrote:
> On Mon, Aug 22, 2005 at 11:53:02AM +0530, Vivek Goyal wrote:
> > On Mon, Aug 22, 2005 at 12:53:10AM +0200, Adrian Bunk wrote:
> > > config CRASH_DUMP
> > > 	bool "kernel crash dumps (EXPERIMENTAL)"
> > > 	depends on EMBEDDED
> > > 	depends on EXPERIMENTAL
> > > 	depends on HIGHMEM
> > > 	help
> > > 	  Generate crash dump after being started by kexec.
> > > 
> > > Two questions:
> > > - If it has any dependencies on kexec, why isn't there a dependency?
> > 
> > crashdump has got dependency on kexec but not in the same kernel. What
> > I mean is that as of today two kernels are involved in this process. First
> > kernel is crashing kernel which should have enabled CONFIG_KEXEC and second
> > kernel (capture kernel) is one which captures the dump and should have
> > CONFIG_CRASH_DUMP enabled. Second kernel need not to have CONFIG_KEXEC
> > enabled for catpturing dump. Hence CRASH_DUMP is not directly dependent
> > on CONFIG_KEXEC.
> 
> Sounds reasonable.
> 
> > > - Is there any sane reason for the dependency on EMBEDDED?
> > > 
> > 
> > I believe this was introduced because large servers can have huge amount
> > of memory (running into Tera Bytes) and saving all that memory might not be
> > practical. Hence it was perceived that until some filtering mechanism is
> > implemented, it is more suited for small systems.
> >...
> 
> It seems you have a wrong impression of what EMBEDDED in the kernel 
> does.
> 

Yes, I misunderstood it.

Thanks
Vivek

      parent reply	other threads:[~2005-08-23  7:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-21 22:53 strange CRASH_DUMP dependencies Adrian Bunk
2005-08-22  6:23 ` Vivek Goyal
2005-08-22  6:40   ` Eric W. Biederman
2005-08-22 20:44   ` Adrian Bunk
2005-08-23  0:56     ` Eric W. Biederman
2005-08-23  7:14     ` Vivek Goyal [this message]

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=20050823071447.GB3766@in.ibm.com \
    --to=vgoyal@in.ibm.com \
    --cc=bunk@stusta.de \
    --cc=ebiederm@xmission.com \
    --cc=fastboot@lists.osdl.org \
    --cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox