mirrors/crosvm
1
0
Fork 0
mirror of https://chromium.googlesource.com/crosvm/crosvm synced 2024-11-24 20:48:55 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions
crosvm/devices/Cargo.toml

119 lines
3.5 KiB
TOML
Raw Normal View History

Move crosvm/hw to a new devices module Moving the devices to their own module makes it easier to add tests that use them. Change-Id: I61bfef4037d16b20145b5fddce604835cdc4f67b Signed-off-by: Dylan Reid <dgreid@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/706559 Reviewed-by: Zach Reizner <zachr@chromium.org>
2017-10-06 22:26:46 +00:00
[package]
name = "devices"
version = "0.1.0"
Fix remaining Chrome/Chromium OS instances These should be written as ChromeOS and ChromiumOS (without the space) to match the updated branding. The copyright headers were already migrated to the new style (https://crrev.com/c/3894243), but there were some more instances left over. BUG=None TEST=tools/cargo-doc Change-Id: I8c76aea2eb33b2e370ab71ee9b5cc0a4cfd00585 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4129934 Reviewed-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
2022-12-29 21:24:33 +00:00
authors = ["The ChromiumOS Authors"]
crosvm: migrate to Rust 2021 edition BUG=none TEST=cq Change-Id: I0059c970879b78bfd40b6ce58b10debcf154b50f Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3508322 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Anton Romanov <romanton@google.com>
2022-03-08 01:16:09 +00:00
edition = "2021"
Move crosvm/hw to a new devices module Moving the devices to their own module makes it easier to add tests that use them. Change-Id: I61bfef4037d16b20145b5fddce604835cdc4f67b Signed-off-by: Dylan Reid <dgreid@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/706559 Reviewed-by: Zach Reizner <zachr@chromium.org>
2017-10-06 22:26:46 +00:00
virtwl: Add DMABuf allocation support. This implements DMABuf allocation type in the virtio wayland device. We attempt to locate a supported DRM device prior to engaging the device jail. If found, the DRM device is passed to the wayland device code and used to serve DMABuf allocations. DMABuf support can be disabled by not providing crosvm with access to any DRM device nodes. The guest is expected to handle the case when DMABuf allocation fails and fall-back to standard shared memory. This initial change uses DRM directly but is structured in a way that would allow the allocator to be replaced by minigbm with minimal effort. BUG=chromium:837209 TEST=crosvm finds drm device and returns valid dmabufs to guest Change-Id: Ic1fd776dfdfefae2d7b321d449273ef269e9cc62 Reviewed-on: https://chromium-review.googlesource.com/1034088 Commit-Ready: David Reveman <reveman@chromium.org> Tested-by: David Reveman <reveman@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org>
2018-04-23 01:42:09 +00:00
[features]
Split arc_quota out of the chromeos feature This allows us to enable the feature in upstream builds. The feature is automatically enabled for the chromeos feature, so it should be a noop for ChromeOS builds. BUG=b:244618505 TEST=presubmit / build_packages implicit-system crosvm Change-Id: I2ea2d668a0f8c2faa92aad5452df0bf660d85e0e Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3919815 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-09-26 21:45:39 +00:00
arc_quota = ["dbus", "protobuf", "system_api"]
Add feature flag for audio. This will allow it to be disabled for Protected KVM usecases on Android. BUG=b:158290206 TEST=cargo test Change-Id: Ibddd8a98c42bb0847aba804f5e33df29feedd783 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2292372 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Tested-by: Dylan Reid <dgreid@chromium.org> Commit-Queue: Andrew Walbran <qwandor@google.com>
2020-03-18 18:00:47 +00:00
audio = []
Integrate audio_streams into crosvm, add stub libcras implementation The `# ignored by ebuild` tag will remove the path to libcras_stub and allows crosvm to be built with the actual libcras implementation. This allows all other platforms to build without depending on `third_party/adhd/cras/client/libcras`, which is a prerequisite for externalizing crosvm. An empty libcras_stub crate is provided to keep cargo happy in external builds. To build with cargo against libcras, the setup_cros_cargo.sh script can be used. BUG=b:191511078 TEST=Tests in crosvm and cros_sdk both pass: $ ./test_all $ cros_run_unit_tests --package=crosvm Cq-Depend: chromium:2993483 Change-Id: I86aad23a86c78e580c1724fb311f870b25d6b09e Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2988154 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Chih-Yang Hsia <paulhsia@chromium.org>
2021-06-23 18:34:31 +00:00
audio_cras = ["libcras"]
crosvm: Make ballooning a compile time feature Balloon support can not be compiled out, and don't need to be disabled at run time. BUG=b:235887451 TEST=Guest has balloon device by default, does not have balloon device when disabled. Ballooning via cli functions by default, return not supported when running vm has ballooning compiled out. Change-Id: I737851496fe4c14cdbb69c48e6edf1ca9186c15a Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3786928 Tested-by: Zihan Chen <zihanchen@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Zihan Chen <zihanchen@google.com>
2022-07-25 23:54:13 +00:00
balloon = []
vmm_vhost: Introduce GPU_MAP Adds a new message that can be used to map GPU memory via Vulkano. BUG=b:244622199 TEST=presubmit & downstream Change-Id: I4018cfda7573d4df2d89225060d5d61c8ac5d3d9 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3924935 Reviewed-by: Gurchetan Singh <gurchetansingh@chromium.org> Commit-Queue: Idan Raiter <idanr@google.com> Reviewed-by: David Stevens <stevensd@chromium.org>
2022-09-29 17:46:42 +00:00
gpu = ["gpu_display"]
devices: irqchip: Implement GunyahIrqChip Implement GunyahIrqChip. Cherry-pick notes: Added license header + delete unused imports. BUG=b:232360323 Change-Id: I11d32599f221b57974f9d942d1aa9f128fc14516 Signed-off-by: Elliot Berman <quic_eberman@quicinc.com> Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4404218 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-10-12 22:33:38 +00:00
gunyah = []
media: libvda: allow to build without linking to libvda libvda is only available on ChromeOS, and being unable to link to it with regular builds reduces our build coverage. Add a "libvda-stub" feature that, if enabled, results in dummy C stubs being build for all the exported libvda functions. This allows builds with the "libvda" feature to pass, although of course the resulting video device would immediately crash and thus should not be used. BUG=b:244619291 TEST=`cargo build --features="video-decoder,video-encoder,libvda-stub"` completes. TEST=`cargo build --features="video-decoder,video-encoder,libvda"` reports link errors against libvda. TEST=`cargo build --features all-x86_64` builds libvda and completes without error. Change-Id: I9bb60f6caf670081d67c91275727f3888272d64b Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3947844 Reviewed-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
2022-10-12 03:18:50 +00:00
libvda-stub = ["libvda/libvda-stub"]
Cargo.toml: introduce net feature This commit just adds the feature but intentionally does not use it yet. For downstream projects (e.g. the ChromeOS crosvm ebuild) that use --no-default-features and enable individual features manually, those projects will need to add the net feature to their build scripts in order to keep network functionality. Once that is done, then we can make the net feature actually control whether the net device is built. Change-Id: I47e405ac295eef933f5d83ec3a4a490028da231b Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4823132 Reviewed-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
2023-08-29 19:50:40 +00:00
net = []
aarch64: MTK GenieZone hypervisor enablement as Crosvm backend To support GenieZone (gz) hypervisor as a crosvm hypervisor backend: - Implement GenieZone hypervisor - Implement GenieZone’s irqchip - Create config and feature for GenieZone - Probe proper hypervisor backend with naive logic - Inject virtual interrupts - Bootup guest VM with linux kernel to shell We still have other todos: - Integrate with protected VM and pvmfw - Support multi-core VM Fixed bugs: - Replace gz with geniezone in most cases for clarity - Replace KVM’s ioctl number with GZVM’s ioctl in bindings Bug: 264630327 TEST: $ taskset 10 ./crosvm run --disable-sandbox -m 512 -s s1 \ --rwroot alpine-rootfs.img -p 'init=/bin/sh rodata=off' \ --display-window-keyboard Image_515_41_no_numa_20230130 \ --serial type=stdout,hardware=serial,earlycon \ --serial type=stdout,hardware=virtio-console,console,stdin Change-Id: Ia5d92ba5cbb4198ab7f9f2a778da03b2199892cd Signed-off-by: Ze-yu Wang <ze-yu.wang@mediatek.com> Signed-off-by: Yi-de Wu <yi-de.wu@mediatek.com> Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4170415 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Frederick Mayle <fmayle@google.com> Commit-Queue: Frederick Mayle <fmayle@google.com>
2023-02-13 04:57:30 +00:00
geniezone = []
devices: add "usb" feature for emulated xHCI Add a default-enabled "usb" feature to allow compiling out the emulated USB controller and host device provider when not needed (e.g. for crosvm-direct). This reduces the crosvm-direct binary size by about 400 KiB. BUG=b:173824333 TEST=cargo build --no-default-features TEST=cargo build # ensure xhci controller is added Change-Id: I1fc0eeb09c647854e5df57cd2fe7e92140256853 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2913136 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Tomasz Jeznach <tjeznach@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
2021-05-21 20:55:10 +00:00
usb = []
video: decoder: vaapi: switch to external cros-codecs Use the version of cros-codecs publishes on crates.io and adapt the code to be able to use it. This results in a few simplifications as e.g. frame ordering is guaranteed by cros-codecs and we don't need to handle it anymore. BUG=b:262824148 TEST=ffmpeg -codec:v vp9_v4l2m2m -i Big_Buck_Bunny_720_10s_1MB.webm Big_Buck_Bunny-%03d.png TEST=cargo test --features "video-decoder,vaapi,ffmpeg" -p devices -- --include-ignored test_decode_h264 Change-Id: Ib694afe8206a4d85b307efaaf3f6669dfe4e18bb Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4518093 Auto-Submit: Alexandre Courbot <acourbot@chromium.org> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
2023-04-28 02:24:39 +00:00
vaapi = ["cros-codecs/vaapi", "downcast-rs", "crc32fast"]
virtio: video: make libvda a selectable feature For the crosvm externalization project, we want to be able to compile video support without libvda, which is only supported on Chrome OS. Add an explicit "libvda" feature to crosvm and make all the libvda code depend on that feature, so any trace of libvda can effectively be compiled out. For compatibility, the "libvda" feature is selected by the "video-decoder" or "video-encoder" features. BUG=b:161774071 BUG=b:169295147 TEST=`cargo build --features="video-decoder,video-encoder"` results in a crosvm binary with libvda enabled. Change-Id: Ice3d3089b73b77f6b009400953063f2cf8f385da Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3026351 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
2021-07-11 14:06:30 +00:00
video-decoder = []
video-encoder = []
rutabaga_gfx: rutabaga_gralloc: a shimmering beacon of hope rutabaga_gralloc is a cross-platform, Rust-based buffer manager. The rationale for this change is: 1) For the {cross-domain, wayland} context type, we need to have a good story for the crucial "wl-dmabuf" feature. As minigbm has been thoroughly tested on ChromeOS and currently powers the "wl-dmabuf" feature, it only makes sense for us to have a path to minigbm for the cross-domain prototype. This will be used by Sommelier. 2) While minigbm allocation works well on Chromebooks, it is not sufficient for cross-platform purposes. For their Virtual Graphics Interface (VGI) initiative, Android graphics virtualization experts have expressed their desire for a Vulkan based allocator. This will to go alongside cros_gralloc in minigbm, which is considered by many to be the ""world's premiere gralloc implementation". 3) Android graphics virtualization experts have expressed their desire for vkMapMemory(..) to be used when crosvm is in multi-process mode. Currently, only dma-buf mmap() is supported for zero-copy blobs in multi-process mode. dma-buf mmap() is not guaranteed to work on Nvidia (a "must have" for Cuttlefish) or any other driver for that matter (we *make* it work for ChromeOS). Possibly only solution: vkMapMemory ;-) With these goals in mind, here's a summary of the revelant changes: * Renamed the {gpu_allocator.rs, GpuMemoryAllocator trait} to be {gralloc.rs, Gralloc trait}. * Moved all GPU allocation out of the resources crate and into the rutabaga_gfx crate. This will allow the resources crate to be focused on managing resources for virtual machines. * Moved the gpu_buffer crate into the gralloc module in the rutabaga_gfx crate. The same functionality is now under "minigbm.rs", "minigbm_bindings.rs" and "rendernode.rs" * Added an optional dependency on vulkano.rs. vulkano.rs is a safe Rust wrapper around the Vulkan api [a]. It's emphasis on type safety makes a good fit for crosvm, though there are other high quality crates out there (gfx-rs, ash.rs). Though development has slowed down, it should satisfy goals (2) and (3) quite easily. * Added a system_gralloc implementation based on memfd. This can be used when minigbm or Vulkano features are not used, to replicate the highly useful "wl-shm" feature in Sommelier. Astute observers will note this can also enable seamless Wayland windowing without GPU features for Android too. Some minor changes to the base crate were needed. * Cut down on the amount of DrmFormats to the subset needed by Sommelier and cros_gralloc. * Moved checked arithmetic into it's own file. * Internally renamed to "wl-dmabuf" feature to be the "minigbm" feature. This is because "wl-dmabuf" has a dependency on minigbm. * Small rutabaga_gfx cleanups [a] https://github.com/vulkano-rs/vulkano/blob/master/DESIGN.md BUG=b:146066070, b:173630595, b:150239451 TEST=launch virtual machine with 2D mode TEST=launch virtual machine with 3D mode TEST=run sommelier with "wl-dmabuf" and "wl-shm" Change-Id: I693a39cef64cd98e56d843d3c60caa7983d4d6e1 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2626487 Tested-by: Gurchetan Singh <gurchetansingh@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Commit-Queue: Gurchetan Singh <gurchetansingh@chromium.org>
2020-12-09 18:44:13 +00:00
minigbm = ["rutabaga_gfx/minigbm"]
rutabaga_gfx: do not support GLX if x feature is not enabled At the moment compiling with the "virgl_renderer" feature enabled but "x" disabled results in a link error because the virgl_renderer enables all its platforms without checking. Fix this by enabling the glx platform only if the x feature has also been enabled. BUG=b:226033718 TEST=`cargo build --features "virgl_renderer"` passes. TEST=`cargo build --features "virgl_renderer,x"` passes and enables GLX in virgl_renderer. Change-Id: I85041fc2a3db7e49415add69389bee3160ba4a5b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3539327 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
2022-03-22 04:36:27 +00:00
x = ["gpu_display/x", "rutabaga_gfx/x"]
crosvm: clearer naming about GPU features It's possible to compile the gpu device without virgl_renderer. In fact, in many instances, this may be required. This builds the gpu device default, but only with --gpu do I see /dev/dri/renderN128, so this should be safe. BUG=b:173630595 TEST=compile and run Cq-Depend: chromium:2592111 Change-Id: I5fbf2de8a2f818a9ca2e5ac4a1a02c7797cff927 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2592089 Tested-by: Gurchetan Singh <gurchetansingh@chromium.org> Tested-by: Daniel Verkamp <dverkamp@chromium.org> Auto-Submit: Gurchetan Singh <gurchetansingh@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Gurchetan Singh <gurchetansingh@chromium.org>
2020-12-14 23:20:45 +00:00
virgl_renderer = ["gpu", "rutabaga_gfx/virgl_renderer"]
devices: add feature flags to render_server_fd. We want to hide this variable from platforms that don't use it. BUG=b:213149288 TEST=presubmit Change-Id: I0d44d2bc50843b86d82b4084f95c8d1a1f750aa6 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3895401 Reviewed-by: Yiwei Zhang <zzyiwei@chromium.org> Commit-Queue: Pujun Lun <lunpujun@google.com> Reviewed-by: Ryan Neph <ryanneph@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Chia-I Wu <olv@google.com>
2022-09-14 19:42:41 +00:00
virgl_renderer_next = ["gpu", "rutabaga_gfx/virgl_renderer_next"]
Extract vtpm out of the chromeos feature And enable it in upstream all-linux builds. The feature is enabled for chromeos by default, so should be a no-op for chromeos builds. We can probably simplify the cfg() attributes further by only enabling the feature for x86, so we do not need the extra check each time. But that'll require ebuild changes. BUG=b:244618505 TEST=presubmit TEST=cargo build --no-default-features --features=vtpm Change-Id: Ibb33c04ab5e6486969fefc6f3e57503be4eccdf3 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3924741 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-09-28 17:32:52 +00:00
vtpm = ["system_api", "protobuf", "dbus"]
rutabaga_gfx: an electrifying possibility rutabaga_gfx is a cross platform, Rust-based, Wayland and Vulkan-centric Virtual Graphics Interface (VGI). Apologies for the mega-change, but it was hard to do this piece by piece. The rationale for this change is: 1) Android graphics virtualization experts have been proposing for a VGI for many months (years?). Their goal is to boot Android anywhere, everywhere. 2) For the {wayland, cross-domain} context type prototype, it's desirable to create a {wayland, camera} connection at the appropriate time. Details can be found in the code, though the RutabagaChannels have yet to be hooked up. There's a high chance neither effort will work. As such, rutabaga is just a prototype. However, even (1) and (2) don't end up working, this refactor/cleanup by itself makes a ton of sense. Here's a summary of revelant changes: * Removed auto-generated {p_defines, p_format, virgl_protocol}. These files were added for tests when bringing up crosvm-gpu, and AFAICT these tests are not run. There's actually now a commit queue for virglrenderer changes and container boot tests that provides excellent coverage. * Removed command_buffer.rs. Used only for the previously mentioned tests. It's quite nice, but couldn't determine the right place to put it. Maybe data_model? But removed it in the interim. * Removed {write_from_guest_memory, read_to_volatile}. The same basic functionality has been moved into {transfer_write, transfer_read} in Rutabaga. * Removed VirtioResource, Virtio3DResource, Virtio2DResource, and VirtioGfxStreamResource in favor of VirtioGpuResource and RutabagaResource. This leads to less duplication and clearer separation between external library functions and VMM functions. * Moved display and hypervisor memory management functions to virtio_gpu.rs. This is because external components do not interface with this functionality, and there was a lot of duplication (for example map/unmap blob). * Added context management between gfxstream and virglrenderer. * Added separate gfxstream and virglrenderer flags. * Clearer naming. * Added simple implementations for context init and multiple timelines. These changes have no effect since all Google kernels don't pass the revelant flags, but are useful for theoretical {wayland, cross-domain} prototype. * Unify RESOURCE_CREATE_3D and RESOURCE_CREATE_2D handling. * Better error handling. BUG=b:146066070, b:173630595, b:150239451 TEST=launch virtual machine with 2D mode TEST=launch virtual machine with 3D mode TEST=boot ARCVM Change-Id: I240b0c134a3b562cbc65981837a41f6db7767c92 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2522452 Tested-by: Gurchetan Singh <gurchetansingh@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Gurchetan Singh <gurchetansingh@chromium.org> Reviewed-by: Lingfeng Yang <lfy@google.com> Reviewed-by: Zach Reizner <zachr@chromium.org>
2020-10-20 01:31:13 +00:00
gfxstream = ["gpu", "rutabaga_gfx/gfxstream"]
balloon: use protos for registered events since the RegisteredEvent model is effectively an external API, switch to using protobuf as a more formal/stable means of communicating messages. also introduces exporting the registered_events.proto file as part of crosvm_control build, alongside the currently existing header file. this patch also introduces feature-gating for registered_events and protos so as not to bring in too many third party dependencies for a base build. BUG=b/278117550 TEST=run bzImage locally TEST=sidecar program available at https://x20.corp.google.com/users/dr/drmasquatch/socket-pinger-proto Change-Id: I5d91d87f7807effc125352caf5c75eee2593f70d Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4521604 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: maciek swiech <drmasquatch@google.com>
2023-05-10 19:10:52 +00:00
registered_events = []
devices: Enable net_util/slirp if slirp is enabled This is needed to build the `devices` crate only for the windows target. BUG=none TEST=cargo test --target=x86_64-pc-windows-gnu --features=slirp in devices Change-Id: I781def962a716e4ee2ea80f3c6d1a426fc92e2e8 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4028759 Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org>
2022-11-08 16:18:43 +00:00
slirp = ["net_util/slirp"]
devices: add bus statistics Collect stats for read and write functions. BUG=b:213149155 TEST=presubmit Change-Id: Ia9d6a5fe006d2377dadde7215a9bf6ecd7966b13 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3773173 Tested-by: Vikram Auradkar <auradkar@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Vikram Auradkar <auradkar@google.com>
2022-07-13 01:02:32 +00:00
stats = []
crosvm: Add seccomp_trace feature Add a minijail's mode of operation where an always-allow seccomp filter is attached to forked device processes. This facilitates capturing seccomp filters used by each device process separately. TESTED=./tools/build_release -- --features seccomp_trace && strace -ff crosvm --log-level debug run <args> BUG=b:258316090 Change-Id: Ic4d3f5178e6a2dcbd748d101db43574f3224ff78 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4289510 Commit-Queue: Zihan Chen <zihanchen@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2023-02-23 23:21:55 +00:00
seccomp_trace = []
swap: expose Status interface to all variants Status does not depend on any swap related feature. Exposing Status to all variants is easy to implement swap status FFI at crosvm_control. The new "swap/enable" feature switches the actual vmm-swap functionality to be compiled. The feature is enabled by default on "swap" crate but disabled on the root package for test dependency. Vmm-swap feature is enabled by `--features=swap` flag on cargo build as before. swap/src/controller.rs is copied from swap/src/lib.rs. BUG=b:265386761 TEST=tools/dev_container tools/run_tests2 Change-Id: Ifc2539a62d0f594fd5bbb41623c735ea2621f7b6 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4486546 Reviewed-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: David Stevens <stevensd@chromium.org>
2023-04-28 06:09:25 +00:00
swap = ["swap/enable"]
irqchip: Add `WhpxSplitIrqChip` implementation Implement `WhpxSplitIrqChip` for `whpx` (Hyper-V) which has a split IRQ chip architecture. Add dependencies for the root `whpx` feature on the `devices/whpx` feature set. BUG=b:213149158 TEST=Compiled on windows. Change-Id: I3b0aec441b5abdff3f0266a9467380b0cdc4fdee Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3717187 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Vaibhav Nagarnaik <vnagarnaik@google.com>
2022-06-21 19:47:16 +00:00
whpx = []
devices: pci: Hotplug compatible PCI trait CL introduces HotPluggable, additional requirements for a PciDevice to be configured in a hotplug context. VirtioPciDevice is currently the only supported type. TEST=tools/presubmit BUG=b:243767476 Change-Id: I0e8a6c6fbd430216874b54d7b577f04cd4bae5fd Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4615383 Reviewed-by: Chih-Yu Huang <akahuang@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Ryuichiro Chiba <chibar@chromium.org> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
2023-06-13 10:48:29 +00:00
pci-hotplug = []
virtwl: Add DMABuf allocation support. This implements DMABuf allocation type in the virtio wayland device. We attempt to locate a supported DRM device prior to engaging the device jail. If found, the DRM device is passed to the wayland device code and used to serve DMABuf allocations. DMABuf support can be disabled by not providing crosvm with access to any DRM device nodes. The guest is expected to handle the case when DMABuf allocation fails and fall-back to standard shared memory. This initial change uses DRM directly but is structured in a way that would allow the allocator to be replaced by minigbm with minimal effort. BUG=chromium:837209 TEST=crosvm finds drm device and returns valid dmabufs to guest Change-Id: Ic1fd776dfdfefae2d7b321d449273ef269e9cc62 Reviewed-on: https://chromium-review.googlesource.com/1034088 Commit-Ready: David Reveman <reveman@chromium.org> Tested-by: David Reveman <reveman@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org>
2018-04-23 01:42:09 +00:00
Move crosvm/hw to a new devices module Moving the devices to their own module makes it easier to add tests that use them. Change-Id: I61bfef4037d16b20145b5fddce604835cdc4f67b Signed-off-by: Dylan Reid <dgreid@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/706559 Reviewed-by: Zach Reizner <zachr@chromium.org>
2017-10-06 22:26:46 +00:00
[dependencies]
vhost: user: Move from getopts to argh. Motivation: get rid of required options vs help boilerplate BUG=n/a TEST=run_tests I've also done some binary size testing as well: Baseline: text data bss dec hex filename 5050303 264640 1072 5316015 511daf crosvm StructOpt: text data bss dec hex filename 5400901 277104 1072 5679077 56a7e5 crosvm StructOpt, default-features = false text data bss dec hex filename 5418437 275872 1072 5695381 56e795 crosvm argh text data bss dec hex filename 5024287 262648 1072 5288007 50b047 crosvm Change-Id: I7ebe09e38d3854c4a0e5c8e3a2aecb123652ce1e Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3339792 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Anton Romanov <romanton@google.com> Auto-Submit: Anton Romanov <romanton@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Anton Romanov <romanton@google.com>
2021-12-13 23:41:47 +00:00
argh = "0.1.7"
Add virtio-snd device with CRAS backend Enable with `--cras-snd`. Verified: Basic playback and capture Missing features: * Getting chmap/jack/stream info from CRAS. They are hardcoded for now. * Jack connect/disconnect notifications from CRAS * Reporting latency bytes to the driver. It is currently hardcoded to 0. BUG=b:179757101 TEST=`aplay` and `arecord` inside a debian img with a 5.10 kernel built with virtio snd support. Launched with crosvm on rammus/kukui/hatch Change-Id: I240000a92418b75b3eb8dcd241ff320214b68739 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2777991 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Woody Chow <woodychow@google.com> Reviewed-by: Chih-Yang Hsia <paulhsia@chromium.org>
2021-03-22 08:49:57 +00:00
async-task = "4"
acpi: refactor the ACPI PM device Add the AML support to generate the S1 table instead of hard coding. Also use the IO allocater to allocate the IO resouce for ACPI PM. BUG=None TEST=boot crosvm by command "crosvm run -s crosvm.sock -m 4096 --cpus 4 --rwdisk rootfs.img -p "root=/dev/vda rootfstype=ext4" vmlinux". Check the S1 capability by "#echo standby > /sys/power/state" from guest side. Linux guest is suspended. And resume linux guest by "#crosvm resume crosvm.sock" from host side. Change-Id: I75b484c44db05f98d49557ba694a1531b57871c1 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2119571 Reviewed-by: Tomasz Jeznach <tjeznach@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Chuanxiao Dong <chuanxiao.dong@intel.corp-partner.google.com>
2020-04-27 08:32:13 +00:00
acpi_tables = {path = "../acpi_tables" }
devices: Merge `vhost_user_devices` library to `devices` crate We originally created `vhost_user_devices` crate so that we'll be able to have device executables there. However, we decided to have vhost-user device as crosvm's subcommand. So, we have no longer a reason to have vhost-user devices as the separate crate. As the first step to remove the vhost_user_devices crate, this CL move its main logic to the devices crate. Note that we add `vhost_user_devices/src/*_device.rs` in this CL as we need to keep the device executables for a while. BUG=b:195495971 TEST=cargo build Change-Id: I355b9cd35214ac0c3d8ffd6fbebc29dd7548fd61 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3070723 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Chirantan Ekbote <chirantan@chromium.org>
2021-08-16 08:02:52 +00:00
anyhow = "*"
virtio-snd: Upstream Window's virtio-snd Playback impl TEST=presubmits and this code works downstream BUG=b:258298873 Change-Id: I7369fb08af474d107d056da8538de86bbc03eeb8 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4015562 Reviewed-by: Chih-Yang Hsia <paulhsia@chromium.org> Commit-Queue: Richard Zhang <rizhang@google.com>
2022-11-09 00:44:17 +00:00
async-trait = "0.1.36"
devices: Add an Ac97 PCI device The Ac97 device provides the guest with an audio playback device. All input devices are stubbed out. Only playback at 48kHz is supported. The device is emulated by `Ac97Dev` which interfaces with the PCI bus. `Ac97Dev` uses `Ac97` to drive audio functions and emulate the device registers. Physical Ac97 devices consist of two parts, the bus master and a mixer. These two sets of registers are emulated by the `Ac97BusMaster` and `Ac97Mixer` structures. `Ac97BusMaster` handles audio samples and uses `Ac97Mixer` to determine the configuration of the audio backend. BUG=chromium:781398 TEST=crosvm run --disable-sandbox --null-audio --rwdisk gentoo.ext4 -c2 -m2048 -p 'root=/dev/vda snd_intel8x0.inside_vm=1 snd_intel8x0.ac97_clock=48000' vmlinux.bin and play audio with aplay -d2 -Dhw:0,0 -f dat /dev/urandom CQ-DEPEND=CL:1402264 CQ-DEPEND=CL:1421588 CQ-DEPEND=CL:1433794 CQ-DEPEND=CL:1432835 Change-Id: I9985ffad753bccc1bf468ebbdacec0876560a5e0 Signed-off-by: Dylan Reid <dgreid@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1366544 Commit-Ready: Chih-Yang Hsia <paulhsia@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Tested-by: Chih-Yang Hsia <paulhsia@chromium.org> Reviewed-by: Chih-Yang Hsia <paulhsia@chromium.org>
2018-12-06 19:47:18 +00:00
audio_streams = "*"
devices: virtio: snd: Implement file backend for VirtioSnd File backend will write audio playback to files. Every PCM playback stream will have its own file. Changes: * Add playback_path and playback_size to virtio::snd::Parameters * Add new file_backend file in virtio::snd * Add virtio-snd arg help. BUG=b:233542268 TEST=run crosvm with --virtio-snd backend=file and call aplay Change-Id: Iaec01f52292f1181b0137fa3c8d8c2b2b9e7cc49 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4306260 Reviewed-by: Chih-Yang Hsia <paulhsia@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2023-03-02 03:06:55 +00:00
audio_util = { path = "../audio_util" }
balloon_control: expose rust API for balloon Add a crate containing an API for controlling the balloon. This is done by reusing the API between the control socket and the balloon device. BUG=b:213962590 TEST=compiles Change-Id: I5d89d5ebee55162d28ba45ca2c49b7083561b916 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3394440 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: David Stevens <stevensd@chromium.org>
2021-11-11 06:37:32 +00:00
balloon_control = { path = "../common/balloon_control" }
Refactoring: Move common/base into base Executes the script in https://crrev.com/c/3530502 BUG=b:223206469 TEST=presubmit Change-Id: Ibeffdc8de0b2270f070e60bb2de8d9fdc78a2a6d Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3530503 Reviewed-by: Vikram Auradkar <auradkar@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-03-16 19:16:04 +00:00
base = { path = "../base" }
usb: add xhci abi. Add xhci abi structs. BUG=chromium:831850 TEST=cargo test Change-Id: I80cf96a2bd52c1db0ebd7e6bdb90b45a5b2d03bd Reviewed-on: https://chromium-review.googlesource.com/1144264 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: Jingkui Wang <jkwang@google.com> Reviewed-by: Dmitry Torokhov <dtor@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org>
2018-07-18 20:26:44 +00:00
bit_field = { path = "../bit_field" }
Upstream windows serial device Bug: b:213149155 Test: cargo test and presubmit Upstream-Crate: devices Change-Id: I1420fee814271dae9502878963872449dae8218e Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3527444 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Vikram Auradkar <auradkar@google.com>
2022-03-16 02:33:27 +00:00
cfg-if = "1.0.0"
Cargo.toml: add version to chrono dependencies The newest chrono version is currently on the 0.4.x branch, but there are preparations to release a 0.5.x version. Explicitly specify a 0.4.x version in our dependencies since there will be backwards-incompatible API breakages in 0.5.x. <https://github.com/chronotope/chrono/issues/970> The exact version chosen (chrono 0.4.19) matches the version we have pinned in Cargo.lock currently and will match any newer 0.4.x releases, so there should be no functional change. BUG=None TEST=cargo build Change-Id: Ifa24a547e435ab4987be9358343e6b25c1385c66 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4774870 Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2023-08-11 18:30:20 +00:00
chrono = { version = "0.4.19", features = [ "serde" ] }
devices: video: decoder: Add a VAAPI decoder backend Add a VAAPI video decoder backend. This backend is able to decode frames by calling into the VAAPI driver in the system. It does so by making use of a libva wrapper crate that exposes a subset of the VA C code in safe Rust. BUG=b:214478588 TEST=virtio::video::decoder::backend::vaapi::tests::test_get_capabilities passes on Hatch. Change-Id: I52ac6b5b915d9c3a9b55381e1076c1b5ac0dfb5c Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3514624 Commit-Queue: Alexandre Courbot <acourbot@chromium.org> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com>
2022-03-09 13:08:56 +00:00
crc32fast = { version = "1.2.1", optional = true }
Refactoring: Move common/cros_async to cros_async This runs the script added in https://crrev.com/c/3533607 BUG=b:22320646 TEST=presubmit Change-Id: I2e7efdb35508d45281f046e64c24aa43e27f2000 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3533608 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com>
2022-03-17 18:26:01 +00:00
cros_async = { path = "../cros_async" }
video: decoder: vaapi: use cros-codecs 0.0.4 The cros-codecs API has changed a lot, and it supports zero-copy decoding as well as HEVC now. BUG=b:262824148 TEST=presubmit Change-Id: Icc2a258642cef012b5640f1c71ccff481b5808f2 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4744560 Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Frederick Mayle <fmayle@google.com> Reviewed-by: Dennis Kempin <denniskempin@google.com> Auto-Submit: Alexandre Courbot <acourbot@chromium.org>
2023-06-29 03:23:44 +00:00
cros-codecs = { version = "0.0.4", optional = true }
devices: add err code for disk image open failed. Adds a new error code for when we fail to open a disk image. Also adds an exit code we were missing upstream. BUG=b:253348635 TEST=intentionally messed up the disk image path and verified we get this error. Change-Id: I197b4c5d80682dd1ee2a42d02df852276d204c17 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3961530 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Noah Gold <nkgold@google.com>
2022-10-17 20:47:21 +00:00
crosvm_cli = { path = "../crosvm_cli" }
Refactoring: Move various general purpose crates to common/ This change contains the results of running ./tools/contib/cargo_refactor.py This will break the next uprev, and needs to be synchronizized with the corresponding ebuild changes in https://crrev.com/c/3248925 BUG=b:195126527 TEST=./tools/run_tests Change-Id: Ied15a1841887bb8f59fba65b912b81acf69beb73 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3248129 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2021-10-27 18:04:03 +00:00
data_model = { path = "../common/data_model" }
fs: Support setting quota project ID A new command line parameter to specify privileged UIDs. If the requester UID is privileged, PassthroughFs uses D-Bus to set quota project ID. BUG=b:190791826 TEST=build Cq-Depend: chromium:3129049,chromium:3129048 Change-Id: Ie27f200e8c651be6a5503f69e7b784c5e8f968ea Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3014623 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Ryo Hashimoto <hashimoto@chromium.org> Reviewed-by: Chirantan Ekbote <chirantan@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2021-06-21 11:59:04 +00:00
dbus = { version = "0.9", optional = true }
Extract disk creation logic out of qcow and src. Bug: b/133432409 Change-Id: Iba25d5f6bb5f60619bb2f5a3d72ddfd3a81650b4 Signed-off-by: Cody Schuffelen <schuffelen@google.com> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/1691460 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com>
2019-07-02 23:54:05 +00:00
disk = { path = "../disk" }
devices: video: decoder: Add a VAAPI decoder backend Add a VAAPI video decoder backend. This backend is able to decode frames by calling into the VAAPI driver in the system. It does so by making use of a libva wrapper crate that exposes a subset of the VA C code in safe Rust. BUG=b:214478588 TEST=virtio::video::decoder::backend::vaapi::tests::test_get_capabilities passes on Hatch. Change-Id: I52ac6b5b915d9c3a9b55381e1076c1b5ac0dfb5c Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3514624 Commit-Queue: Alexandre Courbot <acourbot@chromium.org> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com>
2022-03-09 13:08:56 +00:00
downcast-rs = { version = "1.2.0", optional = true }
enumn: switch to upstream crates.io version Developers may need to manually clean up the common/enumn directory - it will be left behind if there are build artifacts (Cargo.lock, target directory, etc.): rm -rf common/enumn BUG=b:205344148 TEST=cargo build TEST=tools/presubmit TEST=emerge-hatch crosvm # with https://crrev.com/c/3265967 Change-Id: I1af3bdd22f40e87895a78a5cbc8033476058c927 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3278774 Reviewed-by: Dennis Kempin <denniskempin@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
2021-11-05 23:07:59 +00:00
enumn = "0.1.0"
virtio: video: decoder: add ffmpeg-based software decoder backend The virtio video decoder device is currently only available under very drastic conditions: a build linked against libvda (a ChromeOS-only library that needs the cros chroot to be built and linked against), and a ChromeOS-flavored Chrome instance running alongside crosvm, so the browser can provide the video decoding service through Mojo. This makes the decoder device very difficult to develop on for non-Chromies, and also for Chromies actually since they will always need a DUT to test it on. This patch introduces an alternative decoder backend based on ffmpeg's libraries that performs decoding on the host's CPU. It supports both guest pages and virtio objects as target, and can be considered a reliable and predictable way to test the decoder in any environment. We introduce our own ffmpeg bindings after a quick state of the art revealed that the existing ones were all unsuitable, either for technical or licensing reasons. Doing so is also not a big effort and does not add any new external crate dependency to crosvm. BUG=b:169295147 TEST=cargo test --features "video-decoder,ffmpeg" -p devices ffmpeg TEST=v4l2r's simple_decoder example decodes test-25fps.h264 properly with the following command: ./simple_decoder test-25fps.h264 /dev/video0 --input_format h264 --save test-25fps.nv12 TEST=ARCVM Android youtube plays videos correctly when the ffmpeg backend is used. Change-Id: Ic9c586193f7939f2a3fe59d009c3666585a8bbc7 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3026355 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Alexandre Courbot <acourbot@chromium.org> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
2022-06-02 02:18:48 +00:00
ffmpeg = { path = "../media/ffmpeg", optional = true }
crosvm: GPU and display arg parsing for Windows. This replaces the handwritten arg parser with the serde_keyvalue based parser. Eventually we will unify the arg parsing with Unix. BUG=b:233676779 TEST=cargo b --features all-msvc64,gpu --no-default-features TEST=cargo t -p vm_control --features all-msvc64,gpu --no-default-features TEST=cargo t -p crosvm sys::windows::config:: --features all-msvc64,gpu --no-default-features Change-Id: I36a563be9767c7e5cbd3ab44f6a9ba23cd64cdb6 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3939033 Commit-Queue: Pujun Lun <lunpujun@google.com> Reviewed-by: Alexandre Courbot <acourbot@chromium.org>
2022-10-07 06:35:27 +00:00
gpu_display = { path = "../gpu_display", optional = true }
vmm_vhost: Introduce GPU_MAP Adds a new message that can be used to map GPU memory via Vulkano. BUG=b:244622199 TEST=presubmit & downstream Change-Id: I4018cfda7573d4df2d89225060d5d61c8ac5d3d9 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3924935 Reviewed-by: Gurchetan Singh <gurchetansingh@chromium.org> Commit-Queue: Idan Raiter <idanr@google.com> Reviewed-by: David Stevens <stevensd@chromium.org>
2022-09-29 17:46:42 +00:00
rutabaga_gfx = { path = "../rutabaga_gfx" }
devices: irqchip: new irqchip module This new module contains the irqchip trait and it's implementations. The irqchips will work with the new hypervisor crate to abstract the interaction between crosvm and kvm. This just defines the irqchip trait and an empty implementation of the KvmKernelIrqChip. BUG=chromium:1077058 TEST=added test for creating a KvmKernelIrqChip and adding a Vcpu to it Change-Id: Ic1609c965e0a057f5a9d4d74f1cae46edb46dcb4 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2197398 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Stephen Barber <smbarber@chromium.org> Commit-Queue: Colin Downs-Razouk <colindr@google.com>
2020-04-30 22:48:47 +00:00
hypervisor = { path = "../hypervisor" }
vfio: Implement PciDevice Trait for vfio device According to kernel Documents/vfio.txt and Documents/vfio-mediated-device.txt,user pass host assigned device or mdev to crosvm through --vfio parameter, vfio module open this device and get this device's information. Implement PciDevice trait on this device, then vfio_pci module could trap guest pci cfg r/w and mmio r/w, and transfer this operation into kernel vfio. Currently the relationship of vfio container:group:device are 1:1:1, in the future it could extend to 1:m:n. BUG=chromium:992270 TEST=none Change-Id: I8006ef65022d56197eaeb464811a59db2ce54b9a Signed-off-by: Xiong Zhang <xiong.y.zhang@intel.corp-partner.google.com> Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/1580458 Reviewed-by: Zach Reizner <zachr@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
2019-04-23 09:14:43 +00:00
kvm_sys = { path = "../kvm_sys" }
Move crosvm/hw to a new devices module Moving the devices to their own module makes it easier to add tests that use them. Change-Id: I61bfef4037d16b20145b5fddce604835cdc4f67b Signed-off-by: Dylan Reid <dgreid@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/706559 Reviewed-by: Zach Reizner <zachr@chromium.org>
2017-10-06 22:26:46 +00:00
libc = "*"
Move libvda to media/libvda As we are going to introduce more media-related crates, reserve the "media" folder as a placeholder for them, starting with the existing libvda. BUG=b:169295147 BUG=b:214478588 TEST=cargo build --features "video-decoder,video-encoder,libvda" Change-Id: I1b2ec65cbba8b735db3d19845c504546fa1c64ca Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3565623 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
2022-04-01 07:03:40 +00:00
libvda = { path = "../media/libvda", optional = true }
gpu_display: add X11 input bindings. Adds bindings to the X11 display window to capture keyboard & mouse input & send it to the guest via an EventDevice. Original implementation by zachr@chromium.org. BUG=chromium:1023975 TEST=None Change-Id: I33156a8ca0b8c610a2080e3b6891cca2a865734b Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/1971121 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Noah Gold <nkgold@google.com> Reviewed-by: Zach Reizner <zachr@chromium.org>
2019-12-17 18:07:11 +00:00
linux_input_sys = { path = "../linux_input_sys" }
devices: vvu: Add VFIO PCI driver for vvu BUG=b:194137301 TEST=build Change-Id: Ib4c6a8c5cca3e270a4236be9bf37df2b170e8eb1 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3295304 Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org>
2022-02-09 16:29:29 +00:00
memoffset = { version = "0.6" }
Move crosvm/hw to a new devices module Moving the devices to their own module makes it easier to add tests that use them. Change-Id: I61bfef4037d16b20145b5fddce604835cdc4f67b Signed-off-by: Dylan Reid <dgreid@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/706559 Reviewed-by: Zach Reizner <zachr@chromium.org>
2017-10-06 22:26:46 +00:00
net_sys = { path = "../net_sys" }
devices: remove unconditional dependency on slirp If we always enable "slirp", then there are new, unwanted dependencies on "libslirp-sys" and "pcap-file" in android. The following line from the [features] section is sufficient to enable it when needed: slirp = ["net_util/slirp"] BUG=b:260604615 TEST=cd devices; cargo test --target=x86_64-pc-windows-gnu --features=slirp Change-Id: I87ff19a0101b9d09f42b11517bee2fef8b83ec3f Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4082148 Reviewed-by: Vikram Auradkar <auradkar@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Frederick Mayle <fmayle@google.com>
2022-12-05 23:47:57 +00:00
net_util = { path = "../net_util" }
devices: Add `tsc` handling Add `tsc` as a device. Includes operations to calibrate and sync the TSC values across the physical cores in order to minimize variations found when moving vcpu threads across cores. BUG=b:234508273 TEST=Compiled. Change-Id: I5c79deebc9471dacf9d6596384ee77a8811a58bc Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3682118 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Vaibhav Nagarnaik <vnagarnaik@google.com>
2022-05-31 22:32:25 +00:00
num-traits = "0.2"
Linux: Make vfio kvm file as global One vm may have one vfio kvm file only, it could be created at vm setup or runtime through vfio-pci hotplug, make it as global to satisfy these two cases. When vfio pci device is removed throgh hotplug out, the vfio group will be removed frome vfio kvm file also, so move it into vfio.rs, so it is could be referenced at vfio group's destroy. And vfio group's destroy is called from vcpu thread, while vfio kvm file is created in main thread, so use OnceCall instead of thread_local. BUG=b:185084350 TEST=Boot a vm with or without passthrough device Change-Id: I780c43a0ac0265f1e6f62578e134d09cbefc3e2f Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3062741 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
2021-07-26 06:49:03 +00:00
once_cell = "1.7.2"
devices: battery: move monitor code out of sys The PowerMonitor trait and the code monitoring it for events is not platform specific, so it can be moved out of sys/unix into the main battery code. BUG=b:213149155 TEST=tools/presubmit --all TEST=emerge-brya crosvm Change-Id: I5c34c0e98009d866d5345fd940ecc7f742da1d2c Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4122803 Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2022-12-22 20:20:41 +00:00
power_monitor = { path = "../power_monitor" }
Cargo.toml: upgrade protobuf 2.x -> 3.x system_api bindings have been regenerated with protobuf 3.2; this should be okay to land before the full ChromeOS system_api migration, since crosvm always uses its own copy of the bindings rather than the ones provided by the dev-rust/system_api package. The protoc-rust crate is replaced with protobuf_codegen in 3.x. BUG=b:277243607 BUG=b:279834784 TEST=tools/dev_container tools/presubmit Change-Id: I6aad45ded2639d7506a7238800584bebab196455 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4405309 Reviewed-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Noah Gold <nkgold@google.com>
2023-04-06 19:45:32 +00:00
protobuf = { version = "3.2", optional = true }
protos: Compile protos for trunks daemon The TPM device will need these protos to communicate TPM commands to the Trunks daemon and receive TPM responses. BUG=chromium:911799 TEST=cargo check TEST=cargo check --features tpm TEST=FEATURES=test emerge-nami crosvm TEST=FEATURES=test USE=crosvm-tpm emerge-nami crosvm TEST=local kokoro CQ-DEPEND=CL:1553610 CQ-DEPEND=CL:1553971 Change-Id: I1a67a7b4a3714236b20a790068ca19129446f71c Reviewed-on: https://chromium-review.googlesource.com/1554982 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: David Tolnay <dtolnay@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: David Tolnay <dtolnay@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2019-04-05 18:56:44 +00:00
protos = { path = "../protos", optional = true }
Cargo: bump all rand dependencies to 0.8 The previous configuration made us pull in three different versions of rand, and depending on "*" is a recipe for API incompatibility. crosvm-fuzz needs to match its rand version to the rand_core used in common/cros_fuzz, so that will be upgraded separately. BUG=b:236978141 TEST=cargo build TEST=emerge-hatch crosvm Change-Id: I655ed3f156e4ac43afa3122596f62e9caa43b4f2 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3722184 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com> Reviewed-by: Noah Gold <nkgold@google.com>
2022-06-23 17:56:04 +00:00
rand = "0.8"
lints: Enforce sorted order for enum variants To avoid wasting time re-sorting these things (CL:1492612). https://docs.rs/remain Disclaimer: I wrote the macro. This CL adds #[sorted] attributes to those Error enums that seemed to have made some effort to be in sorted order. TEST=cargo check TEST=cargo check --all-features TEST=cargo check --target aarch64-unknown-linux-gnu TEST=emerge-nami crosvm TEST=local kokoro CQ-DEPEND=CL:1524247 Change-Id: I89685ced05e2f149fa189ca509bc14c70aebb531 Reviewed-on: https://chromium-review.googlesource.com/1515998 Commit-Ready: ChromeOS CL Exonerator Bot <chromiumos-cl-exonerator@appspot.gserviceaccount.com> Tested-by: David Tolnay <dtolnay@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: David Tolnay <dtolnay@chromium.org>
2019-03-11 19:36:30 +00:00
remain = "*"
Move gpu allocator to resources Combine GPU buffer allocation with the system resource allocator making life easier as only one allocator needs to get passed to the execute function. Change-Id: I199eb0fd6b99b629aaec1ae3295e8a1942da5309 Signed-off-by: Dylan Reid <dgreid@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1099856
2018-06-07 22:42:41 +00:00
resources = { path = "../resources" }
replace all usage of MsgOnSocket derives Replaced all usage of MsgSocket with Tube. BUG=b:176847362 TEST=run_tests Change-Id: Ie647f79926bc0414c125a776eafe7f60c071bab2 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2710324 Auto-Submit: Zach Reizner <zachr@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Zach Reizner <zachr@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org>
2021-01-07 16:30:28 +00:00
serde = { version = "1", features = [ "derive" ] }
Add vhost-user-gpu-device BUG=b:179755651 TEST=`glxinfo -B | grep virgl` inside a crostini vm Cq-Depend: chromium:2988140 Change-Id: Ib4102e887650b9dda97debb4c6b4737f0b0a642f Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2987594 Tested-by: Chirantan Ekbote <chirantan@chromium.org> Reviewed-by: Gurchetan Singh <gurchetansingh@chromium.org> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Chirantan Ekbote <chirantan@chromium.org>
2021-06-25 09:30:34 +00:00
serde_json = "1"
crosvm: move run command to argh Due to the way we allow arguments to be specified I was not able to reuse Config structure for cmdline arguments. (eg we allow multiple ways to specify same config) There is still some usage of arguments mod that we need to cleanup later. Change-Id: Ia0c12d508d0a10d17f58944de71276e5984d69ee Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3684144 Auto-Submit: Anton Romanov <romanton@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Anton Romanov <romanton@google.com>
2022-06-01 19:31:29 +00:00
serde_keyvalue = { path = "../serde_keyvalue", features = ["argh_derive"] }
Use small vector optimization WaitContext and Reader/Writer are in the critical path for every device. Use small vector optimization to avoid making unnecessary small heap allocations. The smallvec crate is maintained by the servo authors and only has an optional dependency on serde. BUG=none TEST=pre-cq Cq-Depend: chromium:2687076 Change-Id: Ic0c57ac949e263b70b76495e3c9121dd8c2e1177 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2684062 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Dylan Reid <dgreid@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
2021-02-10 08:50:57 +00:00
smallvec = "1.6.1"
Refactoring: Move various general purpose crates to common/ This change contains the results of running ./tools/contib/cargo_refactor.py This will break the next uprev, and needs to be synchronizized with the corresponding ebuild changes in https://crrev.com/c/3248925 BUG=b:195126527 TEST=./tools/run_tests Change-Id: Ied15a1841887bb8f59fba65b912b81acf69beb73 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3248129 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Dennis Kempin <denniskempin@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2021-10-27 18:04:03 +00:00
sync = { path = "../common/sync" }
system_api: Add copy of ChromeOS's system_api Adds a script that copies the bindings we need upstream. We cannot use the original repository, as it's part of the large platform2 git repository, and the original build.rs depends on ChromeOS tooling to generate these bindings. So instead, this change adds a script that can be called from a chromiumos checkout of crosvm to update the upstream bindings. This allows us to enable certain features that talk to ChromeOS dbus services. They won't be functional upstream, but at least we can compile and test the code. To make things more consistent, we no longer replace the crate with the ChromeOS version when building for ChromeOS. BUG=b:244618505 TEST=presubmit Change-Id: I504cbf6d12b0cb50d9935f5e49b7fa72b692d45c Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3919814 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
2022-09-26 21:20:48 +00:00
system_api = { path = "../system_api", optional = true }
Add the VioS audio backend It only supports playback streams, with capture streams to be added in a different change. BUG=b/171602855 Change-Id: Id9a5a560506f8fd026ef3ed83f8d14b29389e329 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2574813 Tested-by: Jorge Moreira Broche <jemoreira@google.com> Commit-Queue: Jorge Moreira Broche <jemoreira@google.com> Auto-Submit: Jorge Moreira Broche <jemoreira@google.com> Reviewed-by: Dylan Reid <dgreid@chromium.org> Reviewed-by: Chih-Yang Hsia <paulhsia@chromium.org> Reviewed-by: Zach Reizner <zachr@chromium.org>
2020-12-03 02:25:53 +00:00
thiserror = "1.0.20"
tracing: rename tracing to cros_tracing. `tracing` conflicts with a crates.io crate. Since we may support tokio tracing in the future, and want to submit some benchmarks against it right now, we should rename our crate. BUG=b:253517247 TEST=presubmit Change-Id: I32bf64a7ce1830e881bd582e4606932782df65c6 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3957598 Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Reviewed-by: Vikram Auradkar <auradkar@google.com> Commit-Queue: Noah Gold <nkgold@google.com>
2022-10-14 22:14:39 +00:00
cros_tracing = { path = "../cros_tracing" }
swap: expose Status interface to all variants Status does not depend on any swap related feature. Exposing Status to all variants is easy to implement swap status FFI at crosvm_control. The new "swap/enable" feature switches the actual vmm-swap functionality to be compiled. The feature is enabled by default on "swap" crate but disabled on the root package for test dependency. Vmm-swap feature is enabled by `--features=swap` flag on cargo build as before. swap/src/controller.rs is copied from swap/src/lib.rs. BUG=b:265386761 TEST=tools/dev_container tools/run_tests2 Change-Id: Ifc2539a62d0f594fd5bbb41623c735ea2621f7b6 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4486546 Reviewed-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Shin Kawamura <kawasin@google.com> Reviewed-by: David Stevens <stevensd@chromium.org>
2023-04-28 06:09:25 +00:00
swap = { path = "../swap" }
Remove virtio-vhost-user (VVU) support This code is unused and untested, while simultaneously making the rest of the virtio device code more complex. Remove it. BUG=b:276993009 TEST=tools/dev_container tools/presubmit Change-Id: I9d44f92419c6912d1735043404d4f64efc95bba4 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4676076 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org> Reviewed-by: Frederick Mayle <fmayle@google.com> Reviewed-by: Junichi Uekawa <uekawa@chromium.org>
2023-07-10 21:38:23 +00:00
vmm_vhost = { path = "../third_party/vmm_vhost", features = ["vmm", "device"] }
Move crosvm/hw to a new devices module Moving the devices to their own module makes it easier to add tests that use them. Change-Id: I61bfef4037d16b20145b5fddce604835cdc4f67b Signed-off-by: Dylan Reid <dgreid@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/706559 Reviewed-by: Zach Reizner <zachr@chromium.org>
2017-10-06 22:26:46 +00:00
virtio_sys = { path = "../virtio_sys" }
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" }
crosvm: Uprev zerocopy to 0.7.x zerocopy 0.7.x has finally released as a stable version, uprev it to allow some remaining structs to be derivable. TEST=CQ BUG=b:300969352 FIXED=b:300969352 Change-Id: I90f0dfb09494f875fef1cd11bfcbd48030846092 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4878761 Auto-Submit: Zihan Chen <zihanchen@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Zihan Chen <zihanchen@google.com>
2023-09-20 19:11:35 +00:00
zerocopy = { version = "0.7", features = ["derive"] }
tempfile: Unify the two tempdir implementations Looks like we ended up with two totally different tempdir implementations: one from CL:520706 and the other from CL:1409705. This CL consolidates them into one implementation. BUG=chromium:974059 TEST=tempfile: cargo test TEST=crosvm: cargo check --all-features TEST=devices: cargo check --tests TEST=sys_util: cargo check --tests TEST=local kokoro TEST=./build_test Cq-Depend: chromium:1574668 Change-Id: Id70e963c9986ed2fc5f160819c4a7f9f16092b3b Signed-off-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1573227 Tested-by: kokoro <noreply+kokoro@google.com> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org>
2019-04-18 04:09:41 +00:00
devices: Conditionally depend on unix only crates BUG=b:213149155 TEST=presubmit Change-Id: I89a1aaf3e171cbd6c1591ae510dd46424d6f8752 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3703221 Reviewed-by: Dennis Kempin <denniskempin@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Vikram Auradkar <auradkar@google.com>
2022-06-10 06:05:46 +00:00
[target.'cfg(unix)'.dependencies]
fuse = {path = "../fuse" }
libcras = { version = "*", optional = true }
minijail = "*"
p9 = "*"
usb_util = { path = "../usb_util" }
vfio_sys = { path = "../vfio_sys" }
vhost: only compile on unix platforms The vhost kernel API is specific to Linux; it doesn't make sense to build it on Windows. Change-Id: I3b8f726f74389f2a3ff78eff43b0c4f312382004 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4437030 Reviewed-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
2023-04-17 21:26:46 +00:00
vhost = { path = "../vhost" }
devices: Conditionally depend on unix only crates BUG=b:213149155 TEST=presubmit Change-Id: I89a1aaf3e171cbd6c1591ae510dd46424d6f8752 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3703221 Reviewed-by: Dennis Kempin <denniskempin@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Vikram Auradkar <auradkar@google.com>
2022-06-10 06:05:46 +00:00
virtio-vhost: Enable handler to be built and tested on Windows Still need to enable: * balloon (try_clone not implemented) * console (Need to enable Serial) * snd (Unix code not conditionally compiled out) * gpu (Waiting for graphics team to upstream) * vhost-user block BUG=b:237011316 TEST=ran "./tools/run_tests --target=host --arch=win64 --verbose" Change-Id: If2b69250477f88ded7176054196107733736786e Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3721868 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Richard Zhang <rizhang@google.com>
2022-06-24 21:57:01 +00:00
[target.'cfg(windows)'.dependencies]
virtio-vhost: Enable block tests Commented out code reference sandbox crate, which still needs to be upstreamed Still need to enable: * balloon (try_clone not implemented) * console (Need to enable Serial) * snd (Unix code not conditionally compiled out) * gpu (Waiting for graphics team to upstream) BUG=b:237011316 TEST=ran "./tools/run_tests --target=host --arch=win64 --verbose" Change-Id: I1b5f7ae575365351184042bc65cffcfd7efe999a Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3721870 Reviewed-by: Noah Gold <nkgold@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Commit-Queue: Richard Zhang <rizhang@google.com>
2022-06-24 22:28:57 +00:00
broker_ipc = { path = "../broker_ipc" }
devices: resync with downstream This closes the deltas between some of the files of the crate. The changes include - Enables building/testing balloon module on windows. - Suppressing dead-code warnings on windows in cross platform files. - u16 to enum fix. - Organizing imports. - Using Descriptor(windows friendly) over RawDescriptor. - Using Option<Tube> instead of Tube. - Fix some args parsing on windows. BUG=213149155 TEST=presubmit and built on windows downstream Change-Id: Idd2ee81384bc5fade610aa864b2c712ea0a0e0d2 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3783010 Tested-by: Vikram Auradkar <auradkar@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Vikram Auradkar <auradkar@google.com> Auto-Submit: Vikram Auradkar <auradkar@google.com>
2022-07-22 02:38:15 +00:00
metrics = { path = "../metrics" }
virtio-vhost: Enable handler to be built and tested on Windows Still need to enable: * balloon (try_clone not implemented) * console (Need to enable Serial) * snd (Unix code not conditionally compiled out) * gpu (Waiting for graphics team to upstream) * vhost-user block BUG=b:237011316 TEST=ran "./tools/run_tests --target=host --arch=win64 --verbose" Change-Id: If2b69250477f88ded7176054196107733736786e Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3721868 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Richard Zhang <rizhang@google.com>
2022-06-24 21:57:01 +00:00
tube_transporter = { path = "../tube_transporter" }
win_audio: build and test win_audio BUG=b:253494168 TEST=presubmit Change-Id: Icb729671a0dcfbc4b6251c69732784de32f6318d Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3988069 Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Auto-Submit: Vikram Auradkar <auradkar@google.com> Commit-Queue: Vikram Auradkar <auradkar@google.com>
2022-10-17 21:24:42 +00:00
win_audio = { path = "../win_audio"}
devices: resync with downstream This closes the deltas between some of the files of the crate. The changes include - Enables building/testing balloon module on windows. - Suppressing dead-code warnings on windows in cross platform files. - u16 to enum fix. - Organizing imports. - Using Descriptor(windows friendly) over RawDescriptor. - Using Option<Tube> instead of Tube. - Fix some args parsing on windows. BUG=213149155 TEST=presubmit and built on windows downstream Change-Id: Idd2ee81384bc5fade610aa864b2c712ea0a0e0d2 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/3783010 Tested-by: Vikram Auradkar <auradkar@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Vikram Auradkar <auradkar@google.com> Auto-Submit: Vikram Auradkar <auradkar@google.com>
2022-07-22 02:38:15 +00:00
win_util = { path = "../win_util"}
virtio-vhost: Enable block tests Commented out code reference sandbox crate, which still needs to be upstreamed Still need to enable: * balloon (try_clone not implemented) * console (Need to enable Serial) * snd (Unix code not conditionally compiled out) * gpu (Waiting for graphics team to upstream) BUG=b:237011316 TEST=ran "./tools/run_tests --target=host --arch=win64 --verbose" Change-Id: I1b5f7ae575365351184042bc65cffcfd7efe999a Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3721870 Reviewed-by: Noah Gold <nkgold@google.com> Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Vikram Auradkar <auradkar@google.com> Commit-Queue: Richard Zhang <rizhang@google.com>
2022-06-24 22:28:57 +00:00
winapi = "*"
virtio-vhost: Enable handler to be built and tested on Windows Still need to enable: * balloon (try_clone not implemented) * console (Need to enable Serial) * snd (Unix code not conditionally compiled out) * gpu (Waiting for graphics team to upstream) * vhost-user block BUG=b:237011316 TEST=ran "./tools/run_tests --target=host --arch=win64 --verbose" Change-Id: If2b69250477f88ded7176054196107733736786e Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3721868 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Noah Gold <nkgold@google.com> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Commit-Queue: Richard Zhang <rizhang@google.com>
2022-06-24 21:57:01 +00:00
devices: Use async from balloon The newly added async primitives allow for increasing the separation of the various tasks performed by balloon. Breaking each task in to an asynchronous function. BUG=chromium:901139 TEST=Boot crosvm, run 'crosvm balloon' to set the balloon size, check 'vmstat' inside the VM to verify the free memory is affected by the balloon growing and shrinking. run crosvm balloon_stats command and ensure that stats are reported correctly. Change-Id: I0ae2be5eb8e4be65b2eb74de90888357af6ecfd4 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/1993163 Tested-by: Keiichi Watanabe <keiichiw@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Chirantan Ekbote <chirantan@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org>
2020-01-09 07:14:08 +00:00
[dependencies.futures]
version = "*"
device: virtio: snd: Add missing handle_irq_resample While running alsa_conformance_test against the virtio-snd device, the driver will randomly stop getting irq events forever. (vp_interrupt will never get called). At the same time, the host device will still see an uncleared `interrupt_status` so the `trigger_interrupt` -> `signal` will just drop the interrupt signal on the host device side. And the device can't be used forever when the issue happens. Root cause: Irq resample events never get handled in the virtio-snd device, so the interrupt handler in guest just can't get notified if there are some unhanded interrupts in the irq line during the resample event. Changes: - Add `f_resample` future in the run_worker - Use `select!` from futures crate with `async-await` feature - Change local interrupt in run_worker to Rc<RefCell<interrupt>> - Use anyhow::Context for errors BUG=b:202368198 TEST=vm.AudioAlsaConformance.virtio_cras_snd TEST=Run alsa_conformance_test multiple times in guest VM Change-Id: Id1440420dcfeccbbb455b1d342863e430ef4b6f9 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3317327 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Chih-Yang Hsia <paulhsia@chromium.org> Reviewed-by: Chirantan Ekbote <chirantan@chromium.org>
2021-12-06 13:42:14 +00:00
features = ["async-await", "std"]
devices: Use async from balloon The newly added async primitives allow for increasing the separation of the various tasks performed by balloon. Breaking each task in to an asynchronous function. BUG=chromium:901139 TEST=Boot crosvm, run 'crosvm balloon' to set the balloon size, check 'vmstat' inside the VM to verify the free memory is affected by the balloon growing and shrinking. run crosvm balloon_stats command and ensure that stats are reported correctly. Change-Id: I0ae2be5eb8e4be65b2eb74de90888357af6ecfd4 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/1993163 Tested-by: Keiichi Watanabe <keiichiw@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Chirantan Ekbote <chirantan@chromium.org> Reviewed-by: Dylan Reid <dgreid@chromium.org>
2020-01-09 07:14:08 +00:00
default-features = false
tempfile: Unify the two tempdir implementations Looks like we ended up with two totally different tempdir implementations: one from CL:520706 and the other from CL:1409705. This CL consolidates them into one implementation. BUG=chromium:974059 TEST=tempfile: cargo test TEST=crosvm: cargo check --all-features TEST=devices: cargo check --tests TEST=sys_util: cargo check --tests TEST=local kokoro TEST=./build_test Cq-Depend: chromium:1574668 Change-Id: Id70e963c9986ed2fc5f160819c4a7f9f16092b3b Signed-off-by: Daniel Verkamp <dverkamp@chromium.org> Reviewed-on: https://chromium-review.googlesource.com/1573227 Tested-by: kokoro <noreply+kokoro@google.com> Legacy-Commit-Queue: Commit Bot <commit-bot@chromium.org>
2019-04-18 04:09:41 +00:00
[dev-dependencies]
devices: video: decoder: Add a VP8 VAAPI decoder Add a VAAPI VP8 backend. It uses the VAAPI driver in the system to decode vp8 frames. BUG=b:214478588 TEST=virtio::video::decoder::backend::vaapi::vp8::tests::test_25fps_vp8 passes on Hatch. Change-Id: I5173a1761d98f0d0b3e4d4fb73c27eb8de87fb42 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3514628 Reviewed-by: Alexandre Courbot <acourbot@chromium.org> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Alexandre Courbot <acourbot@chromium.org>
2022-04-12 22:51:26 +00:00
bytes = "1.1.0"
virtio: video: decoder: add ffmpeg-based software decoder backend The virtio video decoder device is currently only available under very drastic conditions: a build linked against libvda (a ChromeOS-only library that needs the cros chroot to be built and linked against), and a ChromeOS-flavored Chrome instance running alongside crosvm, so the browser can provide the video decoding service through Mojo. This makes the decoder device very difficult to develop on for non-Chromies, and also for Chromies actually since they will always need a DUT to test it on. This patch introduces an alternative decoder backend based on ffmpeg's libraries that performs decoding on the host's CPU. It supports both guest pages and virtio objects as target, and can be considered a reliable and predictable way to test the decoder in any environment. We introduce our own ffmpeg bindings after a quick state of the art revealed that the existing ones were all unsuitable, either for technical or licensing reasons. Doing so is also not a big effort and does not add any new external crate dependency to crosvm. BUG=b:169295147 TEST=cargo test --features "video-decoder,ffmpeg" -p devices ffmpeg TEST=v4l2r's simple_decoder example decodes test-25fps.h264 properly with the following command: ./simple_decoder test-25fps.h264 /dev/video0 --input_format h264 --save test-25fps.nv12 TEST=ARCVM Android youtube plays videos correctly when the ffmpeg backend is used. Change-Id: Ic9c586193f7939f2a3fe59d009c3666585a8bbc7 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3026355 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Alexandre Courbot <acourbot@chromium.org> Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
2022-06-02 02:18:48 +00:00
crc32fast = "1"
devices: Force to run Passthroughfs integration tests in single thread We can't run PassthroughFS unit in multithreaded environment because each test creates its own PassthroughFS and the difference instances can execute conflicting process-wide operations (e.g. fchdir). So, we need to have an integration test binary with a custom test harness. BUG=b:275016855 TEST=run_tests --dut=host TEST=run_tests -p mingw64 Change-Id: I33855ab37bbe9486723038ed196f50a1a85ca748 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4369818 Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2023-03-24 06:46:46 +00:00
libtest-mimic = "0.6"
devices: virtio: Serialize PassthroughFs unit tests with NamedLock Use NamedLock to prevent PassthroughFs tests from running in multi-threads when one runs `cargo test`. Previously, we ran these tests as a part of integration tests with `libtest_mimic` to ensure it's not parallelized. But, using nextest's feature is more straightforward. Also, running them as unit tests allow us to call mocked functions with `#[cfg(test)]` in the future. Note that NamedLock is not necessary for `cargo nextest` because it runs each test single-threaded, but in multi-processes. BUG=b:275016855 BUG=b:277302336 TEST=run_tests Change-Id: I3751b712eaf1b2180bf4153ab501a32b402c0a29 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4406098 Reviewed-by: Dennis Kempin <denniskempin@google.com> Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org>
2023-04-06 11:21:31 +00:00
named-lock = "0.3"
devices: Force to run Passthroughfs integration tests in single thread We can't run PassthroughFS unit in multithreaded environment because each test creates its own PassthroughFS and the difference instances can execute conflicting process-wide operations (e.g. fchdir). So, we need to have an integration test binary with a custom test harness. BUG=b:275016855 TEST=run_tests --dut=host TEST=run_tests -p mingw64 Change-Id: I33855ab37bbe9486723038ed196f50a1a85ca748 Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4369818 Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org> Reviewed-by: Dennis Kempin <denniskempin@google.com>
2023-03-24 06:46:46 +00:00
tempfile = "3"
Reference in a new issue Copy permalink