[lkml]   [2006]   [Dec]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH] free initrds boot option
> >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.

We've been using the --devicetreeblob kexec-tools option available for
POWERPC. This enables you to setup the device tree (and hence, the
initrd points) as you like.

I'm happy to put together a patch for kexec-tools. Unfortunately this
is arch specific. A quick look through the x86, ia64, s390 and ppc64
code shows the --initrd option for all these just reads the specified
initrd file, pushes it out to memory and uses the base and size pointers
to setup the next boot. We'd obviously just skip to the last stage.

So what's the kexec-tools option called? --initrd-location <base> <size>?

(BTW I'm offline soon, so I probably won't get to this for a few weeks)

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

The above should allow us to do these checks in kexec-tools.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2006-12-08 00:35    [W:0.048 / U:8.132 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site