Skip to content

drm_hwcomposer: Introduce dumpsys metrics

To make optimal performance/power consumption ratio we want to use composing by
dedicated hardware to merge as much as possible composition cases.
We are going to continuously optimize and improve drm_hwcomposer HAL, that
makes high demand on formal validation process.

Introduce "pixel operation" definition. It should be in direct ratio with power
consumption, but currently it roughly calculated as sum of pixels merged by
each layer.
In some future we should apply some average gains depending of operation type
to calculate pixops more precisely. (e.g. scaling should take more pixops than
blending, and blending should take more that copying, etc.).
Using pixops could be very helpful when drm_hwc HAL have a choice which layer
sets to merge by GPU, making possible minimal energy model based planning.

Create statistics of the following events:

  1. Total frames count
  2. Total pixel operations
  3. Pixel operations validated to use GPU (CLIENT)
  4. Calculate composer efficiency: DEVICE/TOTAL operations ratio
  5. Failed atomic validation commits count
  6. Failed atomic presenting commits count


  • $ adb shell dumpsys SurfaceFlinger
    Statistics will be shown at the end of the dump in 2 forms:
  1. Since system launched
  2. Since last dumpsys command called

Using statistics for the regression slope monitoring example:

  1. Boot the board without the change
  2. Use touch or keyboard (avoid using of mouse pointer) to do some predefined actions (open application, start video, etc.)
  3. Save the metrics
  4. Boot the board with the change
  5. Do exactly the same actions as in (2)
  6. Save the metrics
  7. Use metrics before and after change to indicate regression slope

This code was used as reference:

API is described in details here:

Edited by Roman Stratiienko

Merge request reports