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
Support for pKVM is being added to all gs101 builds starting with T,
disabled by default. So far, the userspace components have been included
only in special _pkvm builds. Include them unconditionally.
Also move BOARD_* variables specifying location and partition size of
pvmfw from vendor board config file here.
This adds 89MB to the size of the system image.
Bug: 192819132
Test: build a gs101 target, check /apex/com.android.virt exists
Change-Id: Ie46b0ad5f45bd4757570b72cb275d002df7b4616
Revert "Include pvmfw variables in all gs101 builds"
Revert submission 16007088-pkvm-apex-gs101
Reason for revert: Fails on checkouts without vendor
Reverted Changes:
I238181780:Include pvmfw variables in all gs101 builds
Iefd7e1dc5:pKVM: Include pvmfw and virt APEX in gs101 builds
Bug: 202827425
Bug: 192819132
Change-Id: I08b0b2ac09f68847ad9bfabc39423de408fa6632
Support for pKVM is being added to all gs101 builds starting with T,
disabled by default. So far, the userspace components have been included
only in special _pkvm builds. Include them unconditionally.
This adds 89MB to the size of the system image.
Bug: 192819132
Test: flash, check /apex/com.android.virt exists
Change-Id: Iefd7e1dc5e0c1f23ff66e8b282c94a3b85f7cc3e
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
Enable building pvmfw.img through PRODUCT_BUILD_PVMFW_IMAGE for products
that currently enable pKVM. Note that the board-provided
BOARD_PREBUILT_PVMFWIMAGE may still overshadow that flag.
Bug: 199831815
Test: m ${ANDROID_PRODUCT_OUT}/pvmfw.img
Change-Id: I47713648b795fd7e0f4c0d5a868a1abafea47588
Note : We should customize in specific device for B3, instead of
override gs101
This reverts commit d326059d567690c4b2ffbaaf3e5c3fd51e5a69aa.
Reason for revert: 201962520
Change-Id: I2be3f5bebf52ee4be4b7bf8c0ce50bb83380f8ee
Add support One-handed mode system properties flag to enable B3
project.
Bug: 200899897
Test: Build a new ROM build to manually test
Change-Id: Ia511f9a298f76589780f258daf657d36c666e206
Add a file "fstab.gs101-fips" alongside the existing "fstab.gs101" in
order to specify different encryption settings in FIPS mode.
"androidboot.fstab_suffix=gs101-fips" on the kernel command line will be
used to select the FIPS fstab when needed.
As the two fstabs should be otherwise identical, generate them from a
template file so that they will stay in sync.
Note that generating the fstabs requires that they be installed as build
system modules rather than via PRODUCT_COPY_FILES, which results in the
vendor_ramdisk copy of the fstabs being installed to system/etc rather
than /. This shouldn't cause any problem, now that Android has been
updated to look for the fstab in this location too.
Bug: 191417025
Change-Id: I1d115e014df8ba2fb83046ac0b9b791597364846
(stopship hack) Roll forward the SPL so that we can test
rollback cases in testing before launch.
Bug: 187105270
Change-Id: Ic0bdb7e3ece264aa42af1965421a485a8f16980b
(stopship hack) Roll forward the SPL so that we can test
rollback cases in testing before launch.
Bug: 187105270
Change-Id: Ia6e75f0b6699f7967d4b92ef973f5ca6af1b5e6a
Revert "Detect factory reset and deleteAllKeys"
Revert "Add deleteAllKeys to IKeystoreMaintenance"
Revert "Enable deleteAllKeys from vold"
Revert "Allow vold to deleteAllKeys in Keystore"
Revert submission 15521094-vold-deleteAllKeys
Reason for revert: Causes infinite loop in Trusty KeyMint
Reverted Changes:
I9c5c54714:Detect factory reset and deleteAllKeys
I2fb0e94db:Allow vold to deleteAllKeys in Keystore
Id23f25c69:Add deleteAllKeys to IKeystoreMaintenance
Ife779307d:Enable deleteAllKeys from vold
I4312b9a11:Enable deleteAllKeys from vold
Bug: 187105270
Change-Id: I0a236e0308b9b8354e669b9261fc22a88a01f743
If vold detects when setting up metadata encryption that there has been
a factory reset, call deleteAllKeys on Keystore to delete old user data.
Bug: 187105270
Test: booted Oriole twice
Change-Id: Ife779307db0fe161c8889f7aaab34e2899a6c9e6
(stopship hack) Freeze the SPL so that we can test more
rollback cases in testing before launch.
Bug: 187105270
Change-Id: Icb475d6c3331d26a6b5314cbb0cdf2cbe1428a27
So devices not supporting CDMA don't include the feature by mistake.
Bug: 194307361
Test: inspect build artifacts - telephony.cdma.xml is included
Change-Id: I0fe3a3624d2cda2b57347402d62e8a16513174e5
Merged-In: I0fe3a3624d2cda2b57347402d62e8a16513174e5
(cherry picked from commit d808d99ce089ca4c7ff4e2abe8ee76b4eeb38a64)
