A. Cody Schuffelen bc50b0420a Use a shared buffer for virtio-console data ... The strategy of passing Vec<u8> types introduced in crrev.com/c/2470376 can cause panics when the receiving side doesn't have the capacity to receive the full buffers produced by crosvm. For example, a virtio-console implementation with only one-byte buffers (https://android-review.googlesource.com/c/1853082) almost always won't have the capacity to receive the full buffers. Using a VecDeque ring buffer allows continually appending data from the input in the read thread and pulling off as much as the guest can handle in the guest communication thread, without sacrificing performance when the guest can handle higher volumes. Bug: b/182849835 Bug: b/203138623 Test: Pass some input with an unbuffered single-character console driver Test: Run CtsKeystoreTestCases against cuttlefish (high volume transfers) Change-Id: I6b52a729d5af82f4626a9b1f29176116299b9297 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3227733 Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Cody Schuffelen <schuffelen@google.com> Reviewed-by: Chirantan Ekbote <chirantan@chromium.org> Reviewed-by: Daniel Verkamp <dverkamp@chromium.org>		2021-10-20 22:17:21 +00:00
..
src	Use a shared buffer for virtio-console data	2021-10-20 22:17:21 +00:00
.build_test_serial	devices: Add simple test for proxy device	2020-11-17 21:05:51 +00:00
Cargo.toml	crosvm: switch to upstream tempfile crate	2021-10-11 18:35:55 +00:00