![]() | |||||||||||
Messages in this thread |
> >>> > Is this an effort to boot an ACPI-mode kernel, > >>> > and then kexec a non-ACPI kernel? > >>> > >>> Yes, > >> > >> Why is this feature needed? > >> There are a number of ways that the resulting kernel may fail, > >> all platform specific. > > > > other os still doesn't have update acpi irq routing support. but has > > broken mptable. > > Which is at least in part a reason to go back to the BIOS manufacturer > and get them to fix their table. Who says it is broken? > I can see a warning coming from the kernel if these two tables are inconsistent > though. Again, there may not *be* an MPS table, and if there is but the interrupt links are programmable, the MPS table may have very little in common with the state of the machine in ACPI mode. I'm sorry, kexec continues to sound like science fiction to me. I don't understand why scribbling on upstream Linux in the name of science fiction makes any sense. I just don't get it. -Len -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/ | ||||||||||
| Last update: 2008-06-19 07:31 [from the cache] ©2003-2008 | |||||||||||