Cc: Dave Hansen <haveblue@...>, Linus Torvalds <torvalds@...>, Tilman Schmidt <tilman@...>, Andrew Morton <akpm@...>, <linux-kernel@...>, Thomas Renninger <trenn@...>, Len Brown <len.brown@...>, Christoph Hellwig <hch@...>, Markus Gaugusch <dsdt@...>, <linux-acpi@...>, Al Viro <viro@...>, Arjan van de Ven <arjanv@...>, Eric Biederman <ebiederm@...>
Why do you think it's necessary to turn off acpi mode? What will not
work if we keep it on all the time?
BTW, let me summarize my understanding of the kexec approach:
* the userspace write the new DSDT (cat my-dsdt-image >
/sys/firmware/acpi/tables/DSDT)
* the kernel don't use this DSDT directly but keeps it somewhere warm
and fuzzy in the RAM
* userspace does a kexec
* the new kernel boots and at some (early) point, dsdt_override() is
called. It detects that the special place in the RAM for a new DSDT is
used. It provides this pointer to ACPI as the new place to read the DSDT.
Dave, am I correctly understanding the scenario you had in mind?
I have pratically no knowledge of kexec. Is there a documented way to
pass big chunk of data from one kernel to another one? How can I do that?
Eric
--
