1. This is simpler, as it can be triggered by logic in the init.rc
2. The old method of probing /dev/kvm fails if non-protected kvm
is enabled: the device will exist, but pkvm is not enable
Bug: 346525496
Test: observe that pkvm is enabled after double reboot
Change-Id: I2f557ed56f13458a288ede34e672692b511b6bc9
Reflect the pKVM experiment status from the property into the misc
partition so the bootloader can apply it next boot. This is only done on
builds that don't have pKVM enabled by default by pkvm_enabler.
Bug: 192819132
Test: set property and observe change in pKVM state at reboot
Change-Id: Ief85fa196f630867d0a0ced7fa4744f0241d41ea
gs101 builds are getting experimental support for pKVM which can be
enabled either using fastboot or with misc_writer. For _pkvm builds we
want the device to automatically enable pKVM for testing. This patch
adds a new early-init service which checks for the presence of /dev/kvm
and if not found, writes to /misc and forces a reboot.
Bug: 192819132
Bug: 202484976
Test: flash a _pkvm build, observe double-reboot, check /dev/kvm exists
Change-Id: I3834b3e4c6118b3f6e4093ce52d5b94117eca29c
