mirrors/crosvm
1
0
Fork 0
mirror of https://chromium.googlesource.com/crosvm/crosvm synced 2024-11-25 05:03:05 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
crosvm/arch/Cargo.toml

26 lines
688 B
TOML
Raw Normal View History

crosvm: create a LinuxArch trait and use it for x86 This creates a trait that different architectures can implement to support running Linux VMs. In the implementation on X86 we remove some error and return errors from lower-level modules as appropriate. These modules now implement the Error trait so we can get meaningful descriptions without an extra error from the calling function. This still keeps all the ifdefs in linux.rs for now until we have another implementation to use for ARM. BUG=chromium:797868 TEST=./build_test passes on all architectures TEST=crosvm runs on caroline Change-Id: If24bcc83e25f9127d6aea68f9272e639296aad8b Reviewed-on: https://chromium-review.googlesource.com/952368 Commit-Ready: Sonny Rao <sonnyrao@chromium.org> Tested-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org>
2018-02-14 06:09:43 +00:00
[package]
name = "arch"
version = "0.1.0"
authors = ["The Chromium OS Authors"]
edition: Update arch crate to 2018 edition Separated out of CL:1513058 to make it possible to land parts individually while the affected crate has no other significant CLs pending. This avoids repeatedly introducing non-textual conflicts with new code that adds `use` statements. TEST=cargo check TEST=cargo check --all-features TEST=cargo check --target aarch64-unknown-linux-gnu Change-Id: Ia9d3297d0c8fd4b34cf6dfb203bb7e382a462579 Reviewed-on: https://chromium-review.googlesource.com/1519688 Commit-Ready: David Tolnay <dtolnay@chromium.org> Tested-by: David Tolnay <dtolnay@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: David Tolnay <dtolnay@chromium.org>
2019-03-13 03:58:22 +00:00
edition = "2018"
crosvm: create a LinuxArch trait and use it for x86 This creates a trait that different architectures can implement to support running Linux VMs. In the implementation on X86 we remove some error and return errors from lower-level modules as appropriate. These modules now implement the Error trait so we can get meaningful descriptions without an extra error from the calling function. This still keeps all the ifdefs in linux.rs for now until we have another implementation to use for ARM. BUG=chromium:797868 TEST=./build_test passes on all architectures TEST=crosvm runs on caroline Change-Id: If24bcc83e25f9127d6aea68f9272e639296aad8b Reviewed-on: https://chromium-review.googlesource.com/952368 Commit-Ready: Sonny Rao <sonnyrao@chromium.org> Tested-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org>
2018-02-14 06:09:43 +00:00
linux: Support GDB remote serial protocol for x86_64 Add a flag '--gdb <port>' to provide GDB remote protocol interface so a developer can attach GDB to the guest kernel. In this CL, we support read/write operations for registers and memories. BUG=chromium:1141812 TEST=Attach gdb and see register values on workstation and intel DUT Change-Id: Ia07763870d94e87867f6df43f039196aa703ee59 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2440221 Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org> Tested-by: Keiichi Watanabe <keiichiw@chromium.org> Auto-Submit: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2020-10-21 06:57:33 +00:00
[features]
Add power_monitor crate. PowerMonitor trait objects can be used as a source of power supply data and will be used by the goldfish battery. This CL includes a powerd backed implementation of PowerMonitor available behind a feature flag which receives updated data over D-Bus. BUG=b:137890633 TEST=observe updated power data in ARCVM's /sys/class/power_supply at the end of this chain Cq-Depend: chromium:2550102 Change-Id: Iacdc9bc7d11454d5b4f5d2639d19281174ad7e20 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2537349 Commit-Queue: Alex Lau <alexlau@chromium.org> Tested-by: Alex Lau <alexlau@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2020-11-10 09:24:04 +00:00
power-monitor-powerd = ["power_monitor/powerd"]
Goldfish battery: add external command interface to set the state Add a new command "battery" which is used to modify the virtual battery/ac status. When there is goldfish battery device model created, the command is able to sent to the goldfish battery monitoring thread. If no, the command won't be sent. The supported commands are: 1. crosvm battery goldfish status <status string> crosvm.sock 2. crosvm battery goldfish health <health string> crosvm.sock 3. crosvm battery goldfish present <number> crosvm.sock 4. crosvm battery goldfish capacity <number> crosvm.sock 5. crosvm battery goldfish aconline <number> crosvm.sock "goldfish" is the battery identifier to specify which virtual battery is going to be modified by this command in case there are multiple virtual batteries in the guest in future. Right now only one goldfish battery is supported. BUG=chromium:1050432 BUG=b:137890633 TEST=create VM with parameter "--battery" or "--battery=type=goldfish" and boot linux guest with goldfish_battery driver enabled. From host side, execute command "#crosvm battery goldfish status discharging crosvm.sock" can make the guest receive an interrupt, and the status sysfs is changed to "Discharging". Also tested the other commands as well. TEST=modified values are visible in ARCVM and interrupts are triggered Change-Id: I82177811a6f2b1960f7895522760ff3b8143163f Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2119574 Tested-by: Alex Lau <alexlau@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Alex Lau <alexlau@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2020-04-27 08:39:33 +00:00
gdb = ["gdbstub"]
linux: Support GDB remote serial protocol for x86_64 Add a flag '--gdb <port>' to provide GDB remote protocol interface so a developer can attach GDB to the guest kernel. In this CL, we support read/write operations for registers and memories. BUG=chromium:1141812 TEST=Attach gdb and see register values on workstation and intel DUT Change-Id: Ia07763870d94e87867f6df43f039196aa703ee59 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2440221 Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org> Tested-by: Keiichi Watanabe <keiichiw@chromium.org> Auto-Submit: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2020-10-21 06:57:33 +00:00
crosvm: create a LinuxArch trait and use it for x86 This creates a trait that different architectures can implement to support running Linux VMs. In the implementation on X86 we remove some error and return errors from lower-level modules as appropriate. These modules now implement the Error trait so we can get meaningful descriptions without an extra error from the calling function. This still keeps all the ifdefs in linux.rs for now until we have another implementation to use for ARM. BUG=chromium:797868 TEST=./build_test passes on all architectures TEST=crosvm runs on caroline Change-Id: If24bcc83e25f9127d6aea68f9272e639296aad8b Reviewed-on: https://chromium-review.googlesource.com/952368 Commit-Ready: Sonny Rao <sonnyrao@chromium.org> Tested-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org>
2018-02-14 06:09:43 +00:00
[dependencies]
acpi: support user provided ACPI SDTs. Enable support for user provided ACPI tables with supplementary system description. Argument --acpi-table shall point to exsting file or pseudo-file with valid ACPI table content. BUG=None TEST=boot Linux kernel with generated SSDT tables. Change-Id: I8eac21da070dcc325884ed888cc7bcb01bc086ce Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2212501 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: Tomasz Jeznach <tjeznach@chromium.org> Commit-Queue: Tomasz Jeznach <tjeznach@chromium.org>
2020-05-21 06:27:59 +00:00
acpi_tables = { path = "../acpi_tables" }
crosvm: create a LinuxArch trait and use it for x86 This creates a trait that different architectures can implement to support running Linux VMs. In the implementation on X86 we remove some error and return errors from lower-level modules as appropriate. These modules now implement the Error trait so we can get meaningful descriptions without an extra error from the calling function. This still keeps all the ifdefs in linux.rs for now until we have another implementation to use for ARM. BUG=chromium:797868 TEST=./build_test passes on all architectures TEST=crosvm runs on caroline Change-Id: If24bcc83e25f9127d6aea68f9272e639296aad8b Reviewed-on: https://chromium-review.googlesource.com/952368 Commit-Ready: Sonny Rao <sonnyrao@chromium.org> Tested-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org>
2018-02-14 06:09:43 +00:00
devices = { path = "../devices" }
linux: Support GDB remote serial protocol for x86_64 Add a flag '--gdb <port>' to provide GDB remote protocol interface so a developer can attach GDB to the guest kernel. In this CL, we support read/write operations for registers and memories. BUG=chromium:1141812 TEST=Attach gdb and see register values on workstation and intel DUT Change-Id: Ia07763870d94e87867f6df43f039196aa703ee59 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2440221 Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org> Tested-by: Keiichi Watanabe <keiichiw@chromium.org> Auto-Submit: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2020-10-21 06:57:33 +00:00
gdbstub = { version = "0.4.0", optional = true }
Use hypervisor abstraction to run VMs Calls to the kvm crate have been replaced by calls to hypervisor and devices::irqchip. Plugin is unchanged and still KVM-specific. x86 creates and configures vcpus on the vcpu thread instead of the main thread. Code that still depends on kvm or kvm_sys: - crosvm_plugin, plugin, and protos use kvm and kvm_sys if built with the plugin feature - devices::VfioGroup does a kvm_sys ioctl - devices::irqchip and hypervisor use kvm_sys. hypervisor uses kvm::Cap and kvm::CpuId internally for now. BUG=chromium:1077058 TEST=runs es2gears_wayland on kukui TEST=runs evince on amd64-generic with kernel and split irqchip TEST=build_test excluding tpm2 TEST=cargo check --features plugin Change-Id: I0068e34da6a5ff0079b1237be1958933bf12ffe4 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2307711 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Steven Richman <srichman@google.com>
2020-06-21 04:45:32 +00:00
hypervisor = { path = "../hypervisor" }
crosvm: create a LinuxArch trait and use it for x86 This creates a trait that different architectures can implement to support running Linux VMs. In the implementation on X86 we remove some error and return errors from lower-level modules as appropriate. These modules now implement the Error trait so we can get meaningful descriptions without an extra error from the calling function. This still keeps all the ifdefs in linux.rs for now until we have another implementation to use for ARM. BUG=chromium:797868 TEST=./build_test passes on all architectures TEST=crosvm runs on caroline Change-Id: If24bcc83e25f9127d6aea68f9272e639296aad8b Reviewed-on: https://chromium-review.googlesource.com/952368 Commit-Ready: Sonny Rao <sonnyrao@chromium.org> Tested-by: Sonny Rao <sonnyrao@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org>
2018-02-14 06:09:43 +00:00
kernel_cmdline = { path = "../kernel_cmdline" }
libc = "*"
io_jail: Remove now that the code lives in aosp/external/minijail io_jail has been migrated to aosp/external/minijail/rust/minijail. This removes the crosvm copy and updates the references to use the new location. BUG=chromium:1096175 TEST=cargo test Cq-Depend: chromium:2254418 Change-Id: I29d5c6178b6faf5e52671cfbe6fc7e51f0d21dd2 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2254298 Tested-by: Allen Webb <allenwebb@google.com> Reviewed-by: Dylan Reid <dgreid@chromium.org> Commit-Queue: Allen Webb <allenwebb@google.com>
2020-06-19 14:19:48 +00:00
minijail = "*"
Goldfish battery: add external command interface to set the state Add a new command "battery" which is used to modify the virtual battery/ac status. When there is goldfish battery device model created, the command is able to sent to the goldfish battery monitoring thread. If no, the command won't be sent. The supported commands are: 1. crosvm battery goldfish status <status string> crosvm.sock 2. crosvm battery goldfish health <health string> crosvm.sock 3. crosvm battery goldfish present <number> crosvm.sock 4. crosvm battery goldfish capacity <number> crosvm.sock 5. crosvm battery goldfish aconline <number> crosvm.sock "goldfish" is the battery identifier to specify which virtual battery is going to be modified by this command in case there are multiple virtual batteries in the guest in future. Right now only one goldfish battery is supported. BUG=chromium:1050432 BUG=b:137890633 TEST=create VM with parameter "--battery" or "--battery=type=goldfish" and boot linux guest with goldfish_battery driver enabled. From host side, execute command "#crosvm battery goldfish status discharging crosvm.sock" can make the guest receive an interrupt, and the status sysfs is changed to "Discharging". Also tested the other commands as well. TEST=modified values are visible in ARCVM and interrupts are triggered Change-Id: I82177811a6f2b1960f7895522760ff3b8143163f Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2119574 Tested-by: Alex Lau <alexlau@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Alex Lau <alexlau@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2020-04-27 08:39:33 +00:00
msg_socket = { path = "../msg_socket" }
cargo: Sort all dependency lists in Cargo.toml This may help reduce cases of conflicts between independent CLs each appending a dependency at the bottom of the list, of which I hit two today rebasing some of my open CLs. TEST=cargo check --all-features Change-Id: Ief10bb004cc7b44b107dc3841ce36c6b23632aed Reviewed-on: https://chromium-review.googlesource.com/1557172 Commit-Ready: David Tolnay <dtolnay@chromium.org> Tested-by: David Tolnay <dtolnay@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2019-04-06 21:30:04 +00:00
resources = { path = "../resources" }
sync: Mutex type with methods that panic instead of return error This CL adds a crate `sync` containing a type sync::Mutex which wraps the standard library Mutex and mirrors the same methods, except that they panic where the standard library would return a PoisonError. This API codifies our error handling strategy around poisoned mutexes in crosvm. - Crosvm releases are built with panic=abort so poisoning never occurs. A panic while a mutex is held (or ever) takes down the entire process. Thus we would like for code not to have to consider the possibility of poison. - We could ask developers to always write `.lock().unwrap()` on a standard library mutex. However, we would like to stigmatize the use of unwrap. It is confusing to permit unwrap but only on mutex lock results. During code review it may not always be obvious whether a particular unwrap is unwrapping a mutex lock result or a different error that should be handled in a more principled way. Developers should feel free to use sync::Mutex anywhere in crosvm that they would otherwise be using std::sync::Mutex. TEST=boot linux Change-Id: I9727b6f8fee439edb4a8d52cf19d59acf04d990f Reviewed-on: https://chromium-review.googlesource.com/1359923 Commit-Ready: David Tolnay <dtolnay@chromium.org> Tested-by: David Tolnay <dtolnay@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org>
2018-12-04 07:37:46 +00:00
sync = { path = "../sync" }
Add "base" crate and transition crosvm usages to it from sys_util For now, this crate simply re-exports all of sys_util, but it will be updated to provide new interfaces when needed. This is the first step to making crosvm not directly depend on sys_util, so that we can make the interface changes we need without fear of negatively affecting (i.e. completely breaking) other usages within chromeos. BUG=b:162363783 TEST=./build_test Change-Id: I7d0aa3d8a1f66af1c7fee8fd649723ef17027150 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2325168 Tested-by: Michael Hoyle <mikehoyle@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Michael Hoyle <mikehoyle@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org>
2020-08-03 03:09:41 +00:00
base = { path = "../base" }
Add logic to setup PIC/IOAPIC. TODO: Route irqfd to PIC/IOAPIC to make them fully work. BUG=chromium:908689 TEST=None Change-Id: I301287b1cf32cfccffce6c52ebbb5e123931178e Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/1945796 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Zhuocheng Ding <zhuocheng.ding@intel.corp-partner.google.com>
2019-12-02 07:50:20 +00:00
vm_control = { path = "../vm_control" }
vm_memory: A crate to hold vm-specific memory objects Move GuestAddress and GuestMemory to a new crate for VM memory. This will make separating sys_util and crosvm independent making it easier to use sys_util functions outside of crosvm. Change-Id: I12e14948ea85754dfa6267b3a3fb32b77ef6796e Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2311251 Auto-Submit: Dylan Reid <dgreid@chromium.org> Commit-Queue: Dylan Reid <dgreid@chromium.org> Tested-by: Dylan Reid <dgreid@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org>
2020-07-21 03:21:11 +00:00
vm_memory = { path = "../vm_memory" }
Add power_monitor crate. PowerMonitor trait objects can be used as a source of power supply data and will be used by the goldfish battery. This CL includes a powerd backed implementation of PowerMonitor available behind a feature flag which receives updated data over D-Bus. BUG=b:137890633 TEST=observe updated power data in ARCVM's /sys/class/power_supply at the end of this chain Cq-Depend: chromium:2550102 Change-Id: Iacdc9bc7d11454d5b4f5d2639d19281174ad7e20 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2537349 Commit-Queue: Alex Lau <alexlau@chromium.org> Tested-by: Alex Lau <alexlau@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2020-11-10 09:24:04 +00:00
power_monitor = { path = "../power_monitor" }
Reference in a new issue Copy permalink