On Fri, Jan 10, 2014 at 02:31:31AM +0100, Rafael J. Wysocki wrote: [..] > > It is a fresh instance of kernel booting and it is initializing its data > > structures fresh. It is *not* re-initializing ACPI in same kernel. > > I know. The problem is that the BIOS is generally not stateless and it > remebers stuff. In particular, there are a few handshakes done during the ACPI > initialization and they cannot be repeated without resetting the BIOS to the > initial state, which basically means a reboot. Agreed that stateless BIOS in general would be a problem with kexec. We already face that issue with UEFI where we can't call set virtual address map again in second kernel and kexec did not work with UEFI for so many years. Thanks to Dave, Borislav and Matt that it will soon be working and we will be passing mappings to second kernel. So even in case of ACPI, if there are things which can't be re-initiliazed in second kernel, we will have to figure that out and selectively fix it by passing that info to second kernel and not ask second kernel to reinitialize it, instead of disabling ACPI completely. > > That is kind of orthogonal to the problem at hand, though. Agreed. Thanks Vivek
