--input motion[path=PATH,host-sensors=BOOL,name=N] is a built-in motion-sensor device, as evdev describes one: INPUT_PROP_ACCELEROMETER,
acceleration on ABS_X/Y/Z (256 per g, +-16 g), angular velocity on ABS_RX/RY/RZ (16 per degree/s), MSC_TIMESTAMP; the same as
example_custom_motion_sensor_config.json. The acceleration is the gravity vector in the screen's frame, as Linux desktops read it
(iio-sensor-proxy: Y negative is "normal", X positive "left-up"): upright at rest, Y is -1 g.
The device reads one end of a socket pair; spawn_motion_feeder writes the other from two sources:
- host-sensors=true: the host's accelerometer and gyroscope at 50 Hz. On Android through the NDK's ASensorManager, loaded from
libandroid.so at run time as the display backend loads SurfaceControl, and negated (Android reports the reaction to gravity).
crosvm runs as root under DroidVM, and the sensor service holds continuous sensors back only from app uids in the background,
so the guest has them whether or not anything is showing it. Elsewhere there is no host source yet.
- path: frames (virtio_input_events ending in SYN_REPORT) from an outside writer, e.g. the app that shows the guest, override the
host's sensors for as long as they keep coming: a second after the last one, or at once when the writer closes, the host's
sensors take over again. A presenter that shows the guest's picture turned, or wants it to see other values, sends its own.
Checked on an Ubuntu 26.04 guest (PCI) on the OnePlus Pad 2: "Crosvm Virtio Motion Sensors 0" with PROP=40, udev
ID_INPUT_ACCELEROMETER=1, absinfo -4096..4096 res 256 and -32768..32767 res 16, about 50 accelerometer and 50 gyroscope frames a
second, values matching Android's own (sensorservice shows crosvm's uid-0 connection at 20 ms); monitor-sensor reports right-up
for the tablet held with its natural right edge up (Android ROTATION_90). Before the negation it said left-up.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012Camiwa7VsPwkhfyscKQ6S
virtio_input_absinfo lacked the spec's fifth field, res (virtio 5.8.4), so a guest saw every axis's evdev resolution as 0. It is
there now: 0 for the built-in devices as before, the host device's own value for an evdev passthrough, and an optional "res" for a
custom device's axis (units per mm for touch, per g for acceleration, per degree/s for angular velocity). Linux's virtio_input
already reads it; a guest reading only min and max is unaffected (the ABS_INFO payload grows from 16 to 20 bytes).
A custom device's axis "min"/"max" may now be negative (-2048), as an accelerometer's are. They were u32, so the only way to say
it was the two's complement (4294965248), which still parses the same.
devices/tests/data/input/example_custom_motion_sensor_config.json describes motion sensors as evdev does (INPUT_PROP_ACCELEROMETER;
ABS_X/Y/Z acceleration at 256 per g, ABS_RX/RY/RZ angular velocity at 16 per degree/s; MSC_TIMESTAMP), which a Linux guest's udev
tags ID_INPUT_ACCELEROMETER; a test checks its signed bounds and resolutions. The book documents both.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012Camiwa7VsPwkhfyscKQ6S
The MPTable is written at a physical offset of 639 KB, which is inside
the region reserved for the Linux kernel setup_data linked list. This is
mostly a theoretical concern, as setup_data is typically not very large,
but to avoid any possibility of a collision, reduce the end of the
setup_data region so that it no longer overlaps the MPTable.
Also add documentation of the MPTable location to the memory layout
page.
BUG=b:398261493
Change-Id: Ie020bdfbec90f04dcf08d3dbe6261a8d8d0b61a5
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/6292279
Reviewed-by: Michał Mazurek <mazurekm@google.com>
Reviewed-by: Dennis Kempin <denniskempin@google.com>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
This allows us to create a base container with just debian packages
installed, which we can pin as we uprev other parts of the dev container
(e.g. rust toolchains).
This prevents a frequent annoyance that new debian testing packages
introduce new problems into the build infra.
To make this happen, the setup scripts have been split and
moved to tools/deps, with shorthands in tools/setup*.
BUG=b:382504192
TEST=presubmit with new container
TEST=tools/setup* on local workstation
Change-Id: I0561378c76a1de026c895dfd4052ced02cb3fe8e
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/6153816
Commit-Queue: Dennis Kempin <denniskempin@google.com>
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Updates both container and testvm to the latest version and
fixes issues arising from that.
- Uprev some runtime dependencies in cloud_init
- Fix testvm Makefile to use same directory for artifacts
as testvm.py
- Run ext2 test_mkfs_xattr as sudo to allow modification of selinux
attributes
- Re-format a couple of files with latest versions of formatters
- Use `cp -u` instead of rsync, because for some mysterious reason
rsync gets permission errors in CI that cannot be reproduced
locally.
BUG=b:395695390
TEST=dev_container presubmit --no-delta all
Change-Id: Idff5bf4b15c21ecce883ae9213c50caa4f548353
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/6254015
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Commit-Queue: Dennis Kempin <denniskempin@google.com>
Generate the appropriate bootloader information structure (either the
Linux boot_params or Multiboot info) depending on the type of kernel.
BUG=b:354053941
TEST=boot x86-64 lk.elf from <https://github.com/littlekernel/lk>
Change-Id: Ie958c483c85450ec2e1b98199f8bd4288c70cbde
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5727077
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
Reviewed-by: Dennis Kempin <denniskempin@google.com>
This simplifies the PVMFW build configuration, since it can use the
default -mcmodel=small code generation option.
BUG=b:375568070
Change-Id: I88ae6e3378eeaf1d540ae5c4b3dd6e8a017d89ea
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/6081940
Reviewed-by: Frederick Mayle <fmayle@google.com>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
Construct a separate guest memory region for each of the traditional PC
memory layout low-memory areas:
- 0 to 640 KB (RAM)
- 640 KB to 1 MB (reserved for memory-mapped devices, BIOS, and ROMs)
- 1 MB+ (RAM up to the 4 GB PCI hole)
This simplifies the e820 memory map generation code (it just copies the
exact layout from guest_mem.regions() and translates the memory type
values) and ensures the layout provided to the guest matches the actual
GuestMemory region layout.
The memory_layout documentation is also updated to reflect the layout
more accurately; the kernel and initrd regions are contained inside the
above-1MB RAM region, not separate regions on their own.
BUG=b:375568070
Change-Id: I1f35694365a0ec9966b4d208190db103b48e9045
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/6086957
Reviewed-by: Frederick Mayle <fmayle@google.com>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
to include properties and axis information. That way any arbitrary
device configuration can be specified.
BUG=b/393195608
TEST=cargo test -p devices virtio::input::tests
Change-Id: Ic70fbcf2c6ca9fe1170ccd61ad61ba8c0dd3fd6e
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/6216819
Auto-Submit: Jorge Moreira <jemoreira@google.com>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Just use static images rather than using client-side JavaScript to
generate the diagrams.
Change-Id: Ia02cef221ad7f35361f34b8d7715d9fc822c1d9c
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/6206903
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
Reviewed-by: Noah Gold <nkgold@google.com>
- Provide info on Magma
- Update diagrams and minors fixes
BUG=392889751
TEST=CI
Change-Id: I86176039888c91e230f6ea61780856234ad9c566
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/6206897
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Commit-Queue: Gurchetan Singh <gurchetansingh@chromium.org>
They should use relative paths for the files. This is documented as the
expected use in https://doc.rust-lang.org/std/macro.include_str.html and
allows us to avoid using CARGO_MANIFEST_DIR in the tests.
BUG=b:370352548
TEST=tools/presubmit
Change-Id: I97ca771c54275859c0c4a293084de68af78ce914
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/6159966
Commit-Queue: Devin Moore <devinmoore@google.com>
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Reviewed-by: Frederick Mayle <fmayle@google.com>
Accidentally listed the CAM base for the MEM base.
Change-Id: I5485678f228f9c13b9d68d4c8498af3bfe094bd4
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/6092549
Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org>
Auto-Submit: Frederick Mayle <fmayle@google.com>
Following up https://crrev.com/c/6042654, which forgot to update a link
name.
BUG=none
TEST=mdbook build
Change-Id: I78a29d633d3f5389e2e0e77e816bc7544fe38f9f
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/6090772
Reviewed-by: Takaya Saeki <takayas@chromium.org>
Commit-Queue: Keiichi Watanabe <keiichiw@chromium.org>
Auto-Submit: Keiichi Watanabe <keiichiw@chromium.org>
This CL added recommendation and example codes for the topic of file
access in unit test.
BUG=b:381319960
TEST=mdbook build
Change-Id: Ia04b91b5db334ffab424a8646f0a7bc91e415cb1
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/6073290
Commit-Queue: Yuan Yao <yuanyaogoog@chromium.org>
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
This CL adds example of custom input config file, and shows it on crosvm
book. The example config file matches with the crosvm's default keyboard
config. A unit test is added to ensure the exmaple config file's
supported events is equivalent to the default keyboards.
The example file could benefit users who wants to create their own
configs by modifying it.
BUG=b:361215918
TEST=mdbook build & check the doc
Change-Id: I655c954dca7dc2aa40bc87aa9192ba35712116e0
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/6033859
Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
Commit-Queue: Yuan Yao <yuanyaogoog@chromium.org>
Currently other virtio input devices's configuration are provided from
part of command line, the rest unconfigured part is hard-coded.
This CL introduces a custom device which can configure its name,
serial_name, supported by config file. Crosvm will read and parse the
config file(json format) and create the VirtioInputConfig while
initializing the input device.
By having the custom input device, we can have more flexibility of
creating devices.
Check parse_input_event_config_success() unit test for example of
configuration file format.
BUG=b:361215918
TEST=cargo test
Change-Id: I49fbc33ea655a7c620f82317d556a5d67e7c2765
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5998932
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Commit-Queue: Yuan Yao <yuanyaogoog@chromium.org>
Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
This replaces the --pci-start option, allowing the size to be optionally
specified. Also, adds support for aarch64.
BUG=b:361390145
Change-Id: I04c1a59e4c955fe1f222b82b558cdbe7bdd40daf
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/6042654
Commit-Queue: Frederick Mayle <fmayle@google.com>
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
The PCI config space is 16 MB (256 bus * 32 dev * 8 func * 256 bytes of
config). Fix the ending address and size in the memory layout
documentation. (The code already correctly had AARCH64_PCI_CFG_SIZE set
to 16 MB, so this is purely a documentation issue.)
Change-Id: Ibbb2c2b15c38d626101ed980580e311519019884
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/6042653
Reviewed-by: Frederick Mayle <fmayle@google.com>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
This doesn't seem to correspond to any devices setup by crosvm. We don't
support an AXI bus. Searching for 0x40000000 doesn't turn up anything
relevant.
BUG=b:361390145
Change-Id: Ica4c5bf6ca7b8b417470c37bffd5790776d4086d
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5984062
Commit-Queue: Frederick Mayle <fmayle@google.com>
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Noticed there's no mention of Rust in the book to build crosvm, so
adding it here.
BUG=N/A
TEST=mdbook build
Change-Id: Id667e1dc4f99e459b0a592fcce69a8f402fd3beb
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5939968
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Auto-Submit: Elie Kheirallah <khei@google.com>
As pKVM and pvmfw development for x86 is ongoing, add initial support
for running VMs with pvmfw as the VM bootloader. For now only support
the --unprotected-vm-with-firmware development flag, for running regular
non-protected VMs with pvmfw, which doesn't require pKVM support.
Similarly to ARM, add a dedicated memory region for pvmfw to the x86-64
memory map. This region is located right below the PCI MMIO memory hole.
Its size is 4MB, like on ARM.
Similarly to ARM, the pvmfw entry point is at the beginning of the pvmfw
image, the normal x86-64 boot protocol is kept as is, and additionally
the VM payload (i.e. kernel) entry point is passed to pvmfw in the %rdi
register. This ABI is a subject to change, the final ABI for x86 pvmfw
is not defined yet.
BUG=b:354676864
TEST=1. Run a VM with "--unprotected-vm-with-firmware pvmfw_test.bin"
where pvmfw_test.bin begins with the "jmp *%rdi" instruction (2 bytes:
0xff 0xe7), i.e. pvmfw immediately jumping to the VM entry point.
Result: VM runs as usual.
2. Run a VM with "--unprotected-vm-with-firmware pvmfw_random.bin" where
pvmfw_random.bin contains just random data. Result: VM crashes.
Change-Id: Ib0ee998a99a0cf352a97222769b87be615419187
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5797353
Commit-Queue: Dmytro Maluka <dmaluka@chromium.org>
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Describe exact memory regions occupied by page tables in the memory
map, not just their offsets.
BUG=b:354676864
TEST=None
Change-Id: I14a9b4480c7b0d002b133481d0735389ad22716f
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5878320
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Commit-Queue: Dmytro Maluka <dmaluka@chromium.org>
The system-installed version of virglrenderer is often too old
to be compatible with crosvm, particularly on some Linux
distributions. To ensure compatibility, add documentation to
manually build and install `virglrenderer` from source
instead of relying on potentially outdated system versions.
Change-Id: I862f8fe82bbb5a45bae540bd70e3e8d7fdd16e1f
Signed-off-by: Dorinda Bassey <dbassey@redhat.com>
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5836695
Commit-Queue: Gurchetan Singh <gurchetansingh@chromium.org>
Reviewed-by: Frederick Mayle <fmayle@google.com>
When constructing a Queue from a QueueConfig, require the caller to pass
the corresponding Interrupt, and remove the &Interrupt argument from the
Queue::trigger_interrupt() function. This prevents mismatches of Queue
and Interrupt, especially in the case of a re-activation after a reset
where the old and new Interrupt are not the same.
BUG=b:360926085
Change-Id: I31ad9704d4963e46f7ce1b7b7a43aec1a92e342d
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5798666
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
Reviewed-by: Frederick Mayle <fmayle@google.com>
Using kumquat no longer requires a separate build,
just an separate environment variable.
BUG=357650978
TEST=none
Change-Id: Ie94da7de0fcc7bdea7e41638d986b69bcf5f6daf
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5799157
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Commit-Queue: Gurchetan Singh <gurchetansingh@chromium.org>
On aarch64, we load BIOS payloads at offset 0x200000 because
cuttlefish's u-boot BIOS requires the FDT at offset zero. However, in a
separate use case, we are loading BIOS payloads that are OK with dynamic
FDT addresses, but might use the Gunyah hypervisor, which currently
requires the payload to be loaded at offset zero. One algorithm can't
satisfy both.
Both the u-boot setup and Gunyah ought to be made more flexible, but it
seems useful to make crosvm's behavior configurable. It lets us adjust
those use cases eventually without causing an immediate backwards
incompatability scramble.
A new "after-payload" mode is included that matches crosvm's RISCV FDT
address behavior and potentially helps with the TODO for >4GB VMs.
BUG=b:353758405
Change-Id: I886f47cf8e0a6b02218794615215a0e972a4ace2
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5740018
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Commit-Queue: Frederick Mayle <fmayle@google.com>
Previously, if `--mem` was set to 100MB and `--swiotlb` to 1MB, then
we'd essentially allocate 101MB of RAM for the guest and tell it about a
single 101MB memory region in the FDT (adjacent regions are merged in
the FDT). In contrast, for hypervisors that don't require static
swiotlb, we'd only allocate 100MB of RAM (and then the guest would need
to choose 1MB of its own memory to dedicate to this purpose).
Now both cases will get the same RAM size.
Removed the swiotlb reference from memory_layout.md since it is part of
the RAM region from the perspective of the guest. The need for the
static swiotlb to be created as a separate memslot is more of a
hypervisor implementation detail I think.
BUG=b:346770542
Change-Id: I60b10521635c16fa77b4320de0e11f03ebeca0c5
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5637774
Reviewed-by: Elliot Berman <quic_eberman@quicinc.com>
Commit-Queue: Frederick Mayle <fmayle@google.com>
Reviewed-by: Richard Zhang <rizhang@google.com>
Document the path of crosvm executable in case of building inside
development container
BUG=None
TEST=mdbook build
Change-Id: Iee0e697cc4d1949b7b02f4f12b4504ec6a1b1862
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5693364
Commit-Queue: Sachin Parekh <sachinparekh@google.com>
Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org>
- How to use Kumquat to run GL/VK apps
- How to contribute to AOSP projects
- Various nits
BUG=b:300140266
TEST=mdbook build
Change-Id: I31a7143ba3ed9ed56c55d7ff56f764dcf2fc3a42
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5683770
Commit-Queue: Gurchetan Singh <gurchetansingh@chromium.org>
Reviewed-by: Dennis Kempin <denniskempin@google.com>
We want to go proper release model.
BUG=none
TEST=none
Change-Id: I56a4e2522f809556710b8762c62104c1a79c0242
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5664541
Auto-Submit: Gurchetan Singh <gurchetansingh@chromium.org>
Reviewed-by: Dennis Kempin <denniskempin@google.com>
Commit-Queue: Dennis Kempin <denniskempin@google.com>
Similar to the root option for virtio-block devices, make it possible
to automatically add a kernel root=/dev/pmem<N> command line parameter
for a pmem device.
BUG=b:340780535
TEST=crosvm run --pmem vm_rootfs.img,root=yes bzImage
Change-Id: I938ca1dcedda1392474a91924c02c4b02f114fe9
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5545760
Reviewed-by: Richard Zhang <rizhang@google.com>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
These have moved back to the www.chromium.org website.
Change-Id: I2e29687a8a074b308249949d4272357ec20af8ba
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5381669
Reviewed-by: Alexandre Courbot <acourbot@chromium.org>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
static is just describing how the binaries are linked; the emulator being used
is the qemu-user, which emulates guest userspace syscall API and uses the host
kernel.
BUG=None
TEST=read it
Change-Id: I8b827498727de4ce85604dc3b9efebd89df56e62
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5308639
Commit-Queue: Junichi Uekawa <uekawa@chromium.org>
Reviewed-by: Ryuichiro Chiba <chibar@chromium.org>
Reviewed-by: Dennis Kempin <denniskempin@google.com>
auradkar@, fmayle@, schuffelen@, and nkgold@ discussed
the guidance for cross platform enums and have decided
to recommend a new pattern for dispatch style enums.
BUG=NONE
TEST=builds
Change-Id: I07ce234753a5c39873ae214d6407181cbd46fcf0
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5369097
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Commit-Queue: Noah Gold <nkgold@google.com>
Reviewed-by: Vikram Auradkar <auradkar@google.com>
Reviewed-by: Frederick Mayle <fmayle@google.com>
Reviewed-by: Cody Schuffelen <schuffelen@google.com>
On Azure Dv3 instances `unrestricted guest` is not available.
This prevents crosvm from booting, because TSS address overlaps
with BIOS memory region when BIOS is larger than ~250K.
This fix allows 16M BIOS maximum size and enables identity map address
which allows crosvm to boot on machines where `unrestricted guest` is
not available.
BUG=None
TEST=tools/presubmit
TEST=Boot an AOSP Cuttlefish VM on Azure (without unrestricted guest) and GCP (with unrestricted guest)
Co-authored-by: Bogdan-Cosmin Chifor <bogdan.chifor@tii.ae>
Co-authored-by: Mikko Koivisto <mikko.koivisto@unikie.com>
Co-authored-by: Myung Kyu Kim <myung.kyu.kim@unikie.com>
Change-Id: Ibf7b6685eca969f5f52dd6e5f3510bf919c14e2c
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5290234
Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>
Add a single --input command-line option that can accomodate all virtio
input device types. This will eventually replace the existing input
options such as --keyboard, --mouse, and --multi-touch. For now, a
deprecation notice is added and the existing options continue to work as
before.
BUG=b:255223604
BUG=b:321746987
Change-Id: I243c76a6e16ee0019b4538a39af0363bdfe32d59
Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/5226605
Reviewed-by: Alexandre Courbot <acourbot@chromium.org>
Commit-Queue: Daniel Verkamp <dverkamp@chromium.org>