VBoot Reference: Make kernel_config a 4K byte block, and move it after the verified boot block.

VBoot Reference: Make kernel_config a 4K byte block, and move it after the verified boot block.

The kernel_config is now stored as a 4K binary block instead of the kconfig_options structure that was being used before. Since the verified boot code doesn't care what kernel config options are (other than the length of the kernel image and for verifying them before the rest of kernel), it is ok to keep them as a blackbox.

This CL also changes the verified boot kernel layout - VBlock Data followed by Kernel Config followed by the Kernel Image. This will allow them to be stored separately, or as a concatenated block (for easy memory mapping during kernel load). This should ease the process of generating a layout for verified boot kernel images which is also compatible with legacy BIOSes that don't support this mechanism.

Finally, there is also a new firmware API function to determine the size of a kernel verified boot block, given a pointer to its beginning (for determining the offset to the kernel config and data).

[Bill Richardson, 2010-04-29 18:14:43]

LGTM

http://codereview.chromium.org/1732022/diff/1/5
File src/platform/vboot_reference/utility/include/kernel_utility.h (right):

http://codereview.chromium.org/1732022/diff/1/5#newcode73
src/platform/vboot_reference/utility/include/kernel_utility.h:73: uint64_t
kernel_len_;
No objection, but I kind of doubt that the kernel will ever be larger than 4G.