commit b8e7cec0d0afae48546681dab71e39346e76f63e
author Pierre-Clément Tosi <ptosi@google.com> Tue Jan 31 22:11:34 2023 +0000
committer Pierre-Clément Tosi <ptosi@google.com> Wed Feb 01 13:28:20 2023 +0000
tree dab1d54a7f46f8ed7b89d6361d8ed9914f738a9b
parent 39ee8bf670af115a7fa4d980b14775cdda6f5c1a

pvmfw: Boot the verified kernel instead of x1

As we currently support receiving the payload address through the DT or
the legacy ABI (i.e. register x1, set by the VMM), make sure that the
kernel address used during verification is the one pvmfw executes as
previously, we were always booting from the x1 value, even if a kernel
location was found in the DT (and verified).

Functionally, this allows pvmfw to boot pVMs spawned by crosvm with
--protected-vm-with-firmware, a mode where pKVM prevents the VMM from
setting other registers than x0 (i.e. where x1 is forced to 0).

Test: crosvm --protected-vm-with-firmware pvmfw.bin <...>
Change-Id: I0b6cd590a49d693a31443bfe8a2e8cce40960acd