diff options
| author | Christian Hergert <christian@sourceandstack.com> | 2026-09-03 17:15:51 -0400 |
|---|---|---|
| committer | Dmitry Osipenko <dmitry.osipenko@collabora.com> | 2026-09-20 21:25:21 +0300 |
| commit | 730f8554f35c5a7c404fbba964a6cf9d45908be5 (patch) | |
| tree | 958f2af63ebc913160e557ac0c5a002743ebd9c6 /tools/perf/scripts/python/stackcollapse.py | |
| parent | b4e30bf687ab5131ca5aa063abda6d0e9ddbc8e4 (diff) | |
| download | linux-730f8554f35c5a7c404fbba964a6cf9d45908be5.tar.gz linux-730f8554f35c5a7c404fbba964a6cf9d45908be5.zip | |
drm/virtio: preserve damage clips for rendered resources
virtio_gpu_plane_atomic_check() unconditionally ignores FB_DAMAGE_CLIPS
when the framebuffer changes. This forces a full resource flush on every
page flip when a compositor rotates through multiple framebuffers, even
when userspace supplies accumulated per-buffer damage.
The full update is required for dumb buffers because their contents are
uploaded per buffer. Rendered resources are already coherent on the host,
so replacing their damage with the full plane only discards useful
information.
Restrict ignore_damage_clips to dumb buffers. This allows damage-aware
compositors to propagate partial updates through RESOURCE_FLUSH while
preserving the existing full-upload behavior for dumb buffers.
Signed-off-by: Christian Hergert <christian@sourceandstack.com>
Reviewed-by: Lyude Paul <lyude@redhat.com>
Signed-off-by: Lyude Paul <lyude@redhat.com>
Signed-off-by: Dmitry Osipenko <dmitry.osipenko@collabora.com>
Link: https://patch.msgid.link/20260903211914.1109100-2-lyude@redhat.com
Diffstat (limited to 'tools/perf/scripts/python/stackcollapse.py')
0 files changed, 0 insertions, 0 deletions