mirror of
https://chromium.googlesource.com/crosvm/crosvm
synced 2025-02-06 02:25:23 +00:00
e55b79102c
Stop using Tube::try_clone() as we want to remove this method. This requires a change in how the GPU device tube is set. Cloning the control tube on the VMM side allowed us to pass only one tube to the GPU device, which received the first message asking for BAR information and then immediately recycled its tube to send VmMemoryRequests. Without cloning, we to create two full Tubes and pass the VmMemory tube as part of the first message to the device. This is a bit more involved but also safer. BUG=b:222379833 BUG=b:221484449 TEST=`cargo run device gpu` replies to the initial message and receives the tube from the VMM process. Change-Id: I5c85c7c54ab7be0eba322d1884da7076398c4095 Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/3499911 Reviewed-by: Keiichi Watanabe <keiichiw@chromium.org> Tested-by: kokoro <noreply+kokoro@google.com> Commit-Queue: Alexandre Courbot <acourbot@chromium.org> |
||
|---|---|---|
| .. | ||
| async_types.rs | ||
| event.rs | ||
| ioctl.rs | ||
| lib.rs | ||
| mmap.rs | ||
| shm.rs | ||
| timer.rs | ||
| tube.rs | ||
| wait_context.rs | ||