Hello, On Fri, Aug 23, 2013 at 03:39:53AM +0800, Zhang Yanfei wrote: > What do you mean by "earlyboot"? And also in your previous mail, I am also > a little confused by what you said "the very first stage of boot". Does > this mean the stage we are in head_32 or head64.c? Mostly referring to the state where we don't have basic environment set up yet including page tables. > If so, could we just do something just as Yinghai did before, that is, Split > acpi_override into 2 parts: find and copy. And in "earlyboot", we just do > the find, and I think that is less of risk. Or we can just do ACPI override > earlier in setup_arch(), not pulling this process that early during boot? But *WHY*? It doesn't really buy us anything substantial. What are you trying to achieve here? "Making ACPI info available early" can't be a goal in itself and the two benefits cited in this thread seem pretty dubious to me. Why are you guys trying to push this convolution when it doesn't bring any substantial gain? Thanks. -- tejun -- To unsubscribe from this list: send the line "unsubscribe linux-doc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
