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. Thanks Haren >Thanks >Vivek >_______________________________________________ >fastboot mailing list >[email protected] >https://lists.osdl.org/mailman/listinfo/fastboot > > _______________________________________________ fastboot mailing list [email protected] https://lists.osdl.org/mailman/listinfo/fastboot
