| commit | 6bf5d2b6b479090e26685f9cb841e853e1370eb4 | [log] [tgz] |
|---|---|---|
| author | Takaya Saeki <takayas@chromium.org> | Thu May 18 19:40:03 2023 +0900 |
| committer | crosvm LUCI <crosvm-scoped@luci-project-accounts.iam.gserviceaccount.com> | Fri May 19 01:34:54 2023 +0000 |
| tree | aa0b409f17f87424d0c6697afaf57cf65aaf9e27 | |
| parent | fb6487f90fb1173e069354a350027df188749b9a [diff] |
io_uring: refactor prep_next_sqe to remove an argument no longer used uring::SubmitQueue has pre-allocated io_vecs field inside it, and prep_next_sqe provides a caller with an io_vec so that the caller doesn't have to allocate an io_vec by itself. This used to be used by add_rw_op before. However, no caller uses this given io_vec, but they allocate io_vec by themselves. This change removes io_vecs from the arguments of prep_next_sqe, and refactor SubmitQueue structure to make it simpler. BUG=None TEST=cargo test -p io_uring. A vm launches by crosvm run --async-executor uring... Change-Id: I07bb2f496d3a2e4ca038a4dd861dd80b87ba41ef Reviewed-on: https://chromium-review.googlesource.com/c/crosvm/crosvm/+/4546822 Commit-Queue: Takaya Saeki <takayas@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>
crosvm is a virtual machine monitor (VMM) based on Linux’s KVM hypervisor, with a focus on simplicity, security, and speed. crosvm is intended to run Linux guests, originally as a security boundary for running native applications on the ChromeOS platform. Compared to QEMU, crosvm doesn’t emulate architectures or real hardware, instead concentrating on paravirtualized devices, such as the virtio standard.
crosvm is currently used to run Linux/Android guests on ChromeOS devices.
