f8e1764bb9
CB:36845 simplified how coreboot finds the RW CBFS after vboot has and eliminated a layer of caching. Unfortunately, we missed the fact that the former cached value didn't exactly match the FMAP section... it was in fact truncated to the data actually used by vboot. That patch unintentionally broke this truncation which leads to performance regressions on certain CBFS accesses. This patch makes use of a new API function added to vboot (CL:1965920) which we can use to retrieve the real firmware body length as before. (Also stop making all the vb2_context pointers const. vboot generally never marks context pointers as const in its API functions, even when the function doesn't modify the context. Therefore constifying it inside coreboot just makes things weird because it prevents you from calling random API functions for no reason. If we really want const context pointers, that's a refactoring that would have to start inside vboot first.) This patch brings in upstream vboot commit 4b0408d2: 2019-12-12 Julius Werner 2lib: Move firmware body size reporting to separate function Change-Id: I167cd40cb435dbae7f09d6069c9f1ffc1d99fe13 Signed-off-by: Julius Werner <jwerner@chromium.org> Reviewed-on: https://review.coreboot.org/c/coreboot/+/37680 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Mathew King <mathewk@chromium.org> |
||
|---|---|---|
| .. | ||
| amd_blobs@cf227316b0 | ||
| arm-trusted-firmware@ace23683be | ||
| blobs@034b278184 | ||
| chromeec@a1afae4e00 | ||
| ffs@3ec70fbc45 | ||
| fsp@9e53d779eb | ||
| intel-microcode@1dd14da6d1 | ||
| libgfxinit@fe7985f2a0 | ||
| libhwbase@bd0ed91cb9 | ||
| opensbi@215421ca61 | ||
| vboot@2843aa62ba | ||