commit | f3441822fb8360cacd2d30bcb6731c2841597fc9 | [log] [tgz] |
---|---|---|
author | Huihong Luo <huisinro@google.com> | Wed Jun 16 15:41:07 2021 -0700 |
committer | Huihong Luo <huisinro@google.com> | Mon Jun 28 21:24:33 2021 +0000 |
tree | 66a638e39d8c5dad43eaf9805fb346fdbfa43539 | |
parent | 75fe7e540bf80a76c48b2f73d9a0aafc0b177458 [diff] [blame] |
Re-introduce debug.sf.latch_unsignaled This pretty much reverts this commit: Ia453eaf895554adbb2fa9c11c2bc8609e1037ea5. Some devices may find this helpful to improve performance, but there is a risk of pipeline stall from misbehaving apps. Bug: 173694115 Test: manual Change-Id: I48c3095061dc106fa08d36b8ef17eccb04fb6eb1
diff --git a/services/surfaceflinger/BufferQueueLayer.cpp b/services/surfaceflinger/BufferQueueLayer.cpp index b236fd2..2fa8936 100644 --- a/services/surfaceflinger/BufferQueueLayer.cpp +++ b/services/surfaceflinger/BufferQueueLayer.cpp
@@ -126,6 +126,11 @@ bool BufferQueueLayer::fenceHasSignaled() const { Mutex::Autolock lock(mQueueItemLock); + + if (SurfaceFlinger::enableLatchUnsignaled) { + return true; + } + if (!hasFrameUpdate()) { return true; }