LKML Archive on
help / color / mirror / Atom feed
From: Haren Myneni <>
Cc: Michael Neuling <>,
	Andrew Morton <>, Al Viro <>,,,
	"H. Peter Anvin" <>
Subject: Re: [Fastboot] [PATCH] free initrds boot option
Date: Thu, 07 Dec 2006 13:40:38 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Vivek Goyal wrote:

>On Thu, Dec 07, 2006 at 02:36:18PM +1100, Michael Neuling wrote:
>>>I would have to agree with this; it also seems a bit odd to me to have
>>>this at all (kexec provides a new kernel image, surely it also
>>>provides a new initrd image???)
>Yes, kexec provides the option --initrd, so that a user can supply an
>initrd image to be loaded along with kernel.
>>The first boot will need to hold a copy of the in memory fs for the
>>second boot.  This image can be large (much larger than the kernel),
>>hence we can save time when the memory loader is slow.  Also, it reduces
>>the memory footprint while extracting the first boot since you don't
>>need another copy of the fs.
>Is there a kexec-tools patch too? How does second kernel know about
>the location of the first kernel's initrd to be reused?
kexec-tools has to be modified to pass the first kernel initrd. On 
powerpc, initrd locations are exported using device-tree. At present, 
kexec-tool ignores the first kernel initrd property values and creates 
new initrd properties if the user passes '--initrd' option to the kexec 
command. So, will be an issue unless first kernel device-tree is passed 
as buffer.

>In general kexec can overwrite all the previous kernel's memory. It
>just knows about the segments the user has passed to it and it will
>place these segments to their destination locations. There are no
>gurantees that in this process some data from first kernel will not
>be overwritten. So it might not be a very safe scheme.
Initrd memory can be excluded like other segments such as RTAS and TCE 
on powerpc. However it is not implemented yet even on powerpc and is an 
issue on other archs.


>fastboot mailing list

  reply	other threads:[~2006-12-07 21:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07  0:18 Michael Neuling
2006-12-07  0:25 ` Randy Dunlap
2006-12-07  0:30 ` Andrew Morton
2006-12-07  0:37   ` H. Peter Anvin
2006-12-07  3:36     ` Michael Neuling
2006-12-07 16:47       ` [Fastboot] " Vivek Goyal
2006-12-07 21:40         ` Haren Myneni [this message]
2006-12-07 23:32           ` Michael Neuling
2006-12-13  1:35             ` [Fastboot] " Horms
2007-02-08 12:35               ` Horms
2007-02-08 22:58                 ` Michael Neuling
2006-12-07  3:56 ` Haren Myneni

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \
    --subject='Re: [Fastboot] [PATCH] free initrds boot option' \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

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).