On Friday 23 March 2012 21:05:46 H. Peter Anvin wrote: > On 03/23/2012 07:29 AM, Thomas Renninger wrote: > > Details can be found in: > > Documentation/acpi/initrd_table_override.txt > > I did not see in this any discussion about how the data format of the > initrd/initramfs gets affected. There are some other things too > (microcode updates, for example) Interesting. > which also would like to get initramfs > data early, and maybe we need to think about how to containerize this > properly. Sounds as if this would get a bigger discussion... I won't be able to come up with a detailed suggestion for such a general initrd format change (that's what you suggest?). I'd be interested to be put to CC and join the discussion, though. This patch only slightly touches x86 initrd specifics: (with Yinhai additions even 3 lines less): arch/x86/kernel/setup.c | 15 ++ arch/x86/mm/init.c | 4 No general initrd code is touched at all, all the rest sits in drivers/acpi/ If there is any initrd change this could easily be adopted. Would be great to see this one pushed into 3.4 before a possibly long taking discussion about bigger initrd layout changes. Thanks, Thomas -- 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
