On Sat, 24 Jan, at 09:26:37PM, Dave Young wrote: > > There's several things I need to ask for help from EFI gurus to see if it is > doable: > > * Make sure in case EFI warm reboot the memory of previous kernel can be > retained. The only way to reserve memory across a reboot is with EFI capsules.
> * How to determine if kernel is boot with EFI warm reboot in stub The presence of a capsule would indicate whether we were invoked from a crash handler. > * What is the right way to pass informations from 1st kernel to 2nd kernel. > Is it ok for saving something with efi variables? EFI capsules would the be most natural mechanism, but you could conceivably do it with EFI variables (there's an upper limit on the size of variable data, though). > * Other possible problems what I missed Support for runtime EFI capsules was rather spotty last time I looked. Things may have moved on, but it's definitely something to watch out for. There have been patches on linux-efi in recent months for making use of EFI capsules, https://lkml.kernel.org/r/[email protected] https://lkml.kernel.org/r/[email protected] I could take a look at resubmitting the first series above if that would be useful for doing kexec across a reset. -- Matt Fleming, Intel Open Source Technology Center -- To unsubscribe from this list: send the line "unsubscribe linux-efi" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
