Hi. Rafael J. Wysocki wrote: > On Thursday, 3 of January 2008, Nigel Cunningham wrote: >> Hi. >> >> Rafael J. Wysocki wrote: >>>> I suppose we can always disable this when we start to support hardware >>>> changing over hibernate (I have ideas in this direction - memory cold >>>> plugging, for a start). >>> Well, if we support such features, we won't be following ACPI any more. >> Mmm. Apparently I'm not as focused on specs as you :). >> >> I was starting to think through whether it could make for a new and much >> faster was to boot live cds - something along the lines of complete >> redetection of hardware and memory cold plugging. Of course it's only in >> the 'I wonder if this would be possible' stage at the mo, but seemed at >> least feasible - keep the e820 tables from boot, make _init routines not >> get thrown away and do something like the kexec device shutdown etc >> around an atomic restore. >> >> I know there'd be limitations, but perhaps worth thinking about... > > Well, what if the new e820 map is incompatible with the old one? In the worst case, you tell the user about it and carry on with the old one. Perhaps this would be the killer for the live cd idea - perhaps e820 maps vary too much, there'd be no possible workaround and this would never be practical. It's worth at least thinking about, though, isn't it? Nigel - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html