crosvm/gpu_display/src
Lingfeng Yang 29cd3fb4bb Bump display_wl buffer count to 3
may help with backpressure in high fps situations

It was found that display.flip() can take a long time, at least if
framebuffer_region() is called, which causes dropped frames. The idea is
that if the server is still using the frame we may have to wait $omeTime
to get it back for drawing the next one, and the wait can be long
compared to the time to copy.

BUG=b/153580313

Change-Id: I00c50479b40383d2329d7eb714248a7154a22aba
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/crosvm/+/2224017
Commit-Queue: Lingfeng Yang <lfy@google.com>
Tested-by: Lingfeng Yang <lfy@google.com>
Reviewed-by: Lingfeng Yang <lfy@google.com>
Reviewed-by: Jason Macnak <natsu@google.com>
Reviewed-by: Zach Reizner <zachr@chromium.org>
2020-07-23 21:28:29 +00:00
..
generated gpu_display: add X11 input bindings. 2020-01-03 20:03:53 +00:00
keycode_converter crosvm: Fix compile warnings 2020-04-15 18:01:31 +00:00
display_wl.c gpu_display: fix dangling NULL pointer in dwl_context_setup 2019-06-24 23:59:06 +00:00
dwl.rs crosvm: add license blurb to all files 2019-04-24 15:51:38 -07:00
event_device.rs Use simple virtio_input_events where possible. 2020-03-06 01:00:39 +00:00
gpu_display_stub.rs Make VolatileSlice ABI-compatible with iovec 2020-05-25 19:14:07 +00:00
gpu_display_wl.rs Bump display_wl buffer count to 3 2020-07-23 21:28:29 +00:00
gpu_display_x.rs Fix VolatileSlice calls in all modules 2020-05-27 04:46:31 +00:00
lib.rs Make VolatileSlice ABI-compatible with iovec 2020-05-25 19:14:07 +00:00