Simon J. Gerraty afc571b1a6 veloader use vectx API for kernel and modules ... The vectx API, computes the hash for verifying a file as it is read. This avoids the overhead of reading files twice - once to verify, then again to load. For doing an install via loader, avoiding the need to rewind large files is critical. This API is only used for modules, kernel and mdimage as these are the biggest files read by the loader. The reduction in boot time depends on how expensive the I/O is on any given platform. On a fast VM we see 6% improvement. For install via loader the first file to be verified is likely to be the kernel, so some of the prep work (finding manifest etc) done by verify_file() needs to be factored so it can be reused for vectx_open(). For missing or unrecognized fingerprint entries, we fail in vectx_open() unless verifying is disabled. Otherwise fingerprint check happens in vectx_close() and since this API is only used for files which must be verified (VE_MUST) we panic if we get an incorrect hash. Reviewed by: imp,tsoome MFC after: 1 week Sponsored by: Juniper Networks Differential Revision: https://reviews.freebsd.org//D23827		2020-03-08 17:42:42 +00:00
..
boot1.chrp
kboot	veloader use vectx API for kernel and modules	2020-03-08 17:42:42 +00:00
ofw	[PowerPC] Fix LLD10 linking of ofw loader on ppc	2020-02-25 00:45:09 +00:00
uboot	[PowerPC] Fix 32-bit ubldr calling convention	2020-01-19 04:13:19 +00:00
Makefile
Makefile.inc