Vaapi decoder: use TRACE_COUNTER_ID2 for "Vaapi frames at client"
This CL addresses two issues: - Extends "Vaapi frames at client" to show used vs available, where ToT only shows the currently used ones, without any reference to its max. - TRACE_COUNTER1/2 is global per-process, which means that when there are multiple Vaapi decoders working, each will update the counter as if in isolation, rendering the measurement meaningless. This CL uses TRACE_COUNTER_ID2 to add an id to each counter, allowing for counter separation [1]. [1] https://i.imgur.com/qq60Xqw.png (https://imgur.com/a/AOcwh78) Bug: 909926, 721674 Change-Id: If7089d8e9ca614912b3965eb46dc552b8c63928f Reviewed-on: https://chromium-review.googlesource.com/c/1356884 Commit-Queue: Miguel Casas <mcasas@chromium.org> Reviewed-by:Daniele Castagna <dcastagna@chromium.org> Cr-Commit-Position: refs/heads/master@{#612819}
Showing
Please register or sign in to comment