[RADV] VK_KHR_timeline_semaphore balloons in runtime
When I try to use VK_KHR_timeline semaphore, the CPU time spent in radv_timeline_find_point_at_least_locked grows over time, especially so when running without vsync.
When running viewer/gltf-viewer of Granite (https://github.com/Themaister/Granite) in a release build, perf looks like this:
My assumption is that the timeline semaphore implementation does a linear search through the list and never manages to remove entries from the list.