Alan Stokes 8d35160ef5 Determine CompOS VM size from properties ... Rather than hard-wiring the max VM size, use properties to allow ART to specify how much is needed by the current ART version, and the hypervisor provider to specify an adjustment to it. Previously we set the maximum to 1 GiB, in an attempt to allow for future growth. Instead set the default in the absence of information from ART to 400 MiB, which is sufficient for current versions with a small amount of additional headroom. Bug: 274597466 Test: atest ComposHostTestCases Test: manual: set bad values, see errors Change-Id: Ibd98b670c2ee800064f8069b64ffa9fd160b7446		2023-03-24 12:09:17 +00:00
..
aidl	[doc] Update the link to the BCC specification	2023-03-01 13:12:41 +00:00
apex	Set future_updatable: false for virt and compos APEXes	2023-01-27 01:56:46 +00:00
apk	…
benchmark	Improve assertion	2023-01-24 12:22:11 +00:00
common	Search for CompOsPayloadApp/EmptyPayloadApp with extensions	2023-03-01 12:01:55 -08:00
compos_key_helper	…
composd	Determine CompOS VM size from properties	2023-03-24 12:09:17 +00:00
composd_cmd	Don't start composd if VMs are not supported	2023-02-15 13:17:56 +00:00
service	Map the failure on enabling fs-verity to the atom	2023-03-20 11:14:49 -07:00
src	rpc_binder: Update users of RpcSession	2022-12-19 09:30:02 +00:00
tests	Logging improvements	2023-02-01 17:45:01 +00:00
verify	Refactor VM config to support different CPU topologies	2023-02-09 08:13:44 +00:00
Android.bp	Drop unnecessary dependencies to libbinder_rpc_unstable	2023-02-17 14:04:35 +09:00