All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jay Lan <jlan@sgi.com>
To: Bernhard Walle <bwalle@suse.de>
Cc: kexec@lists.infradead.org
Subject: Re: Memory needed for a kdump kernel has been bloated
Date: Thu, 21 Aug 2008 14:00:24 -0700	[thread overview]
Message-ID: <48ADD768.4040506@sgi.com> (raw)
In-Reply-To: <20080821224119.4d93da1c@kopernikus.site>

Bernhard Walle wrote:
> * Jay Lan <jlan@sgi.com> [2008-08-21 13:35]:
>> 2) the kdump kernel tried to add disk /dev/sdb when it is not even
>>    in /etc/fstab. I think only the system disk and the disk where
>>    we want to save the vmcore to should be needed.
> 
> But what has that to do with the kernel? What do you mean with "add
> disk"? Mount? Load driver? That's up to initrd and/or system
> configuration ...

Hmm, it would be great if there is a way we can initialize only the
needed disk. "add_disk" was called from sd_probe:
   add_disk <-
     sd_probe <-
     driver_probe_device <-
     __device_attach <-
     bus_for_each_drv <-
     ...

So the solution might need come from initrd or a device driver? Maybe
we can use a new system configuration item. But it can save a lot of
memory if we do not need to initialize those devices.

Regards,
 - jay
> 
> 
> 
> Bernhard


_______________________________________________
kexec mailing list
kexec@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/kexec

  reply	other threads:[~2008-08-21 21:00 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-08-21 20:35 Memory needed for a kdump kernel has been bloated Jay Lan
2008-08-21 20:41 ` Bernhard Walle
2008-08-21 21:00   ` Jay Lan [this message]
2008-08-22  6:44     ` Bernhard Walle
2008-08-21 20:41 ` Bernhard Walle
2008-08-21 23:31 ` Neil Horman

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=48ADD768.4040506@sgi.com \
    --to=jlan@sgi.com \
    --cc=bwalle@suse.de \
    --cc=kexec@lists.infradead.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 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.