mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2025-02-11 12:35:26 +00:00
These values are either written by the device and read by the guest or vice versa. Either way, since these could happen simultaneously on separate cores we need fences to prevent the CPU from re-ordering loads and stores. "get" methods use acquire-load semantics while "set" methods use release-store semantics. This also matches what we were already doing for "get_avail_index" and "set_used_index". With this it should be possible to re-enable the check for VIRTIO_AVAIL_F_NO_INTERRUPT but we'll do that in a separate change since we need these changes no matter what. BUG=none TEST=crostini.Basic.buster_stable Change-Id: I2d52c92fbd7ab0fe6d64693d60f46d0dec4b4cb5 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3026685 Tested-by: kokoro <noreply+kokoro@google.com> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org> Commit-Queue: Chirantan Ekbote <chirantan@chromium.org> |
||
---|---|---|
.. | ||
src | ||
.build_test_serial | ||
Cargo.toml |