Lines Matching refs:kernel
38 Otherwise, it hands over the pVM to the guest kernel by jumping to its first
70 image (recorded in the `kernel_size` field), as it already does for the kernel
291 [dice-dt]: https://www.kernel.org/doc/Documentation/devicetree/bindings/reserved-memory/google%2Cop…
358 - the kernel in the `/config` DT node _e.g._
363 kernel-address = <0x80200000>;
364 kernel-size = <0x1000000>;
380 [Linux ABI]: https://www.kernel.org/doc/Documentation/arm64/booting.txt
384 After verifying the guest kernel, pvmfw boots it using the Linux ABI described
414 pvmfw verifies the guest kernel image (loaded by the VMM) by re-using tools and
416 kernel region (see `/config/kernel-{address,size}` described above) to contain
420 avbtool add_hash_footer --image <kernel.bin> \
427 do so, it must be covered by a hash descriptor in the VBMeta of the kernel:
435 avbtool add_hash_footer --image <kernel.bin> \
443 hash descriptor to be added to the kernel footer and that the unsigned
454 kernel][soong-udroid]).