Hi Nico, > Will it be possible to configure a system to do a fast reboot after a > panic? (Also, it might be possible to save less than a full crash dump > and let the system handle the rest of the crash dump after the fast > reboot.)
Not yet, because the current Fast Reboot implementation relies on devices to quiesce. Depending where the panic occurred, it might not be possible to call the device quiesce code. Being able to fast reboot post panic is one of the project's goals, so we are actively investigating and experimenting with various implementations to allow us to fast reboot post panic. For instance, we have been looking into leveraging capabilities of the PCI framework to save and restore the PCI config space and resetting devices. With regard to how to handle crash dump, one of the ideas being considered is to always load a good kernel into memory (if there's sufficient memory, which will be released if freemem is low). On panic, do the regular crash dump, then remap the range of memory that the good kernel is in to be the usual kernel virtual memory. Another idea we are experimenting with is to keep track of the physical memory ranges being used, which we can already do, then pass that information to the new kernel via the memory list. Those ranges of memory will not be used until the content has been saved. We are still at experimental stage with post panic fast reboot. The final implementation might differ. Thanks, -- Sherry Moore, Solaris Core Kernel http://blogs.sun.com/sherrym
