A broad collection of companies are now using LinuxBoot for their firmware. They are still running into kexec issues involving drivers that don't correctly shut down, start up, or still need the BIOS to set magic, undocumented bits.
We have to be able to mark drivers and associated code as "LinuxBoot Ready." This might be done in Kconfig with an option that would only present those drivers know to work with kexec.
But what does "work with" mean?
The goal of this talk is to discuss where LinuxBoot is now in use; what problems have been seen; and how we can deal with them.
|I agree to abide by the anti-harassment policy