| /packages/modules/Virtualization/docs/ |
| D | getting_started.md | 113 [2023-07-07T14:50:43.420766770+09:00 INFO crosvm] crosvm started.
114 [2023-07-07T14:50:43.422545090+09:00 INFO crosvm] CLI arguments parsed.
115 [2023-07-07T14:50:43.440984015+09:00 INFO crosvm::crosvm::sys::unix::device_helpers] Trying to att…
116 [2023-07-07T14:50:43.441730922+09:00 INFO crosvm::crosvm::sys::unix::device_helpers] Trying to att…
117 [2023-07-07T14:50:43.462055141+09:00 INFO crosvm::crosvm::sys::unix::device_helpers] Trying to att…
|
| D | custom_vm.md | 78 IMPORTANT: DO NOT USE `vmlinuz.bin` for passing to crosvm. It doesn't pick-up the correct `init` pr…
261 if [ "$(getprop ro.crosvm.network.setup.done)" == 1 ]; then
269 setprop ro.crosvm.network.setup.done 1
|
| /packages/modules/Virtualization/demo_native/ |
| D | README.md | 53 [2023-05-10T23:45:54.904181191+09:00 INFO crosvm] crosvm started.
54 [2023-05-10T23:45:54.906048663+09:00 INFO crosvm] CLI arguments parsed.
59 [2023-05-10T23:45:58.263614461+09:00 INFO crosvm] exiting with success
|
| /packages/modules/Virtualization/rialto/src/ |
| D | main.rs | 51 layout::{self, crosvm},
96 crosvm::MEM_START..layout::MAX_VIRT_ADDR, in try_main()
97 crosvm::MMIO_RANGE, in try_main()
105 .alloc(fdt_addr, NonZeroUsize::new(crosvm::FDT_MAX_SIZE).unwrap())?; in try_main()
|
| /packages/modules/Virtualization/pvmfw/src/ |
| D | entry.rs | 35 layout::{self, crosvm},
93 let fdt_size = NonZeroUsize::new(crosvm::FDT_MAX_SIZE).unwrap(); in new()
226 crosvm::MEM_START..layout::MAX_VIRT_ADDR, in main_wrapper()
227 crosvm::MMIO_RANGE, in main_wrapper()
|
| /packages/modules/Virtualization/apex/ |
| D | Android.bp | 127 // crosvm and virtualizationservice are only enabled for 64-bit targets on device
131 "crosvm",
142 "crosvm",
|
| D | canned_fs_config_sys_nice | 2 /bin/crosvm 0 3013 0755 capabilities=0x800000 # CAP_SYS_NICE
|
| /packages/modules/Virtualization/virtualizationmanager/src/ |
| D | atom.rs | 18 use crate::crosvm::VmMetric;
205 rssCrosvmKb: rss.crosvm, in write_vm_exited_stats_sync()
|
| D | crosvm.rs | 253 pub crosvm: i64, field
689 Rss { vm: max(x.vm, y.vm), crosvm: max(x.crosvm, y.crosvm) } in extract_max()
767 Ok(Rss { vm: rss_vm_total, crosvm: rss_crosvm_total }) in get_rss()
|
| D | main.rs | 20 mod crosvm; module
|
| /packages/modules/Virtualization/libs/android_display_backend/aidl/android/crosvm/ |
| D | ICrosvmAndroidDisplayService.aidl | 17 package android.crosvm;
|
| /packages/modules/Virtualization/zipfuse/ |
| D | Cargo.toml | 8 fuse = { path = "../../../../external/crosvm/fuse" }
|
| /packages/modules/Virtualization/virtualizationservice/vfio_handler/ |
| D | Android.bp | 11 // Only build on targets which crosvm builds on.
|
| /packages/modules/Virtualization/vmbase/ |
| D | README.md | 4 binaries to run in an aarch64 VM under crosvm (via the VirtualizationService), such as for pVM
66 UART at base address `0x3f8`, the first UART allocated by crosvm), and make a PSCI `SYSTEM_OFF` call
70 `vmbase::power::reboot`. Either will cause crosvm to terminate the VM, but by convention we use
|
| /packages/modules/Virtualization/libs/android_display_backend/ |
| D | Android.bp | 4 "aidl/android/crosvm/ICrosvmAndroidDisplayService.aidl",
|
| D | crosvm_android_display_client.cpp | 27 using aidl::android::crosvm::BnCrosvmAndroidDisplayService;
|
| /packages/modules/Virtualization/vmbase/src/ |
| D | layout.rs | 17 pub mod crosvm; module
|
| /packages/modules/Virtualization/compos/apex/ |
| D | composd.rc | 22 # We need SYS_NICE in order to allow the crosvm child process to use it.
|
| /packages/modules/Virtualization/virtualizationmanager/ |
| D | Android.bp | 14 // Only build on targets which crosvm builds on.
|
| /packages/modules/Virtualization/virtualizationservice/ |
| D | Android.bp | 14 // Only build on targets which crosvm builds on.
|
| /packages/modules/Virtualization/docs/debug/ |
| D | gdb_kernel.md | 9 and `vm run-microdroid` commands. The `crosvm` will start the gdb server on the
|
| D | README.md | 101 device tree from crosvm.
|
| /packages/modules/Virtualization/pvmfw/ |
| D | README.md | 297 pvmfw is intended to run in a virtualized environment according to the `crosvm`
298 [memory layout][crosvm-mem] for protected VMs and so it expects to have been
337 [crosvm-mem]: https://crosvm.dev/book/appendix/memory_layout.html
|
| /packages/modules/Virtualization/microdroid/ |
| D | README.md | 171 digest, and passes to the VM via crosvm option. The vendor hashtree digest is
|
| /packages/modules/Virtualization/vmlauncher_app/java/com/android/virtualization/vmlauncher/ |
| D | MainActivity.java | 22 import android.crosvm.ICrosvmAndroidDisplayService;
|