On 03/24/2012 03:21 PM, H. Peter Anvin wrote: > The attached cpio-parsing code compiles to 458 bytes on x86-64 and 476 > bytes on i386, and that is without any library dependencies at all. > Again, it will completely stop at the first compressed data item, so any > such kernel objects absolutely will have to be first. In good Linux > tradition, it is also completely untested. > > However, given that very reasonable size I would think that this is a > reasonable approach. Anyone who has a better suggestion for the > namespace than "kernel/"? > The more I think about it the more I really think this is the right approach. For microcode, this means we don't have to worry about creating a super-container for the various microcode formats; we can simply have: kernel/x86/microcode/GenuineIntel kernel/x86/microcode/AuthenticAMD ... which solves the problem neatly. It does beg the question if you want to be able to have multiple: kernel/acpi/... ... files, to make managing different tables easier, or is that overkill? -hpa -- 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
