commit | 08bdcdd5ce654bf9235a2df9cc37b33ede6d6afc | [log] [tgz] |
---|---|---|
author | Alan Stokes <alanstokes@google.com> | Wed Feb 22 13:39:10 2023 +0000 |
committer | Alan Stokes <alanstokes@google.com> | Wed Feb 22 14:02:27 2023 +0000 |
tree | 896919e474653ff715a59e76deb724c635f4e2ec | |
parent | bad9de346f9d72059e793df5e994dcb048214e0e [diff] |
Optimize identical configs While writing a demo app I realized it makes sense to call vm.setConfig immediately after vmm.getOrCreate - so if the VM already existed but had a different config, we update it to what we want, or find out it's incompatible. And if in fact we just created the VM it would make sense for setConfig to do minimal work, since old and new config will be the same object. Bug: 243512240 Test: atest MicrodroidTests Change-Id: I0732eec3cd68ef9ad8d4e7b143ce49c46096f82b
This repository contains userspace services related to running virtual machines on Android, especially protected virtual machines. See the getting started documentation and Microdroid README for more information.