summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/net_dropmonitor.py
diff options
context:
space:
mode:
authorNoralf Trønnes <noralf@tronnes.org>2022-11-30 20:26:50 +0100
committerNoralf Trønnes <noralf@tronnes.org>2022-12-06 16:35:22 +0100
commitf531d198822a4bdf631f080a9638096681f6eb9f (patch)
treefdcf99f3fa8bc6446279633fe1c4e2e9cd745514 /tools/perf/scripts/python/net_dropmonitor.py
parent951df98024f7272f85df5044eca7374f5b5b24ef (diff)
drm/gud: Don't retry a failed framebuffer flush
If a framebuffer flush fails the driver will do one retry by requeing the worker. Currently the worker is used even for synchronous flushing, but a later patch will inline it, so this needs to change. Thinking about how to solve this I came to the conclusion that this retry mechanism was a fix for a problem that was only in the mind of the developer (me) and not something that solved a real problem. So let's remove this for now and revisit later should it become necessary. gud_add_damage() has now only one caller so it can be inlined. Reviewed-by: Javier Martinez Canillas <javierm@redhat.com> Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de> Signed-off-by: Noralf Trønnes <noralf@tronnes.org> Link: https://patchwork.freedesktop.org/patch/msgid/20221122-gud-shadow-plane-v2-2-435037990a83@tronnes.org
Diffstat (limited to 'tools/perf/scripts/python/net_dropmonitor.py')
0 files changed, 0 insertions, 0 deletions