On 23/03/17 03:19 AM, Zachary Michaels wrote: > We were experiencing an infinite loop due to VRAM bos getting added back > to the VRAM lru on eviction via ttm_bo_mem_force_space, Can you share more details about what happened? I can imagine that moving a BO from CPU visible to CPU invisible VRAM would put it back on the LRU, but next time around it shouldn't hit this code anymore but get evicted to GTT directly. Was userspace maybe performing concurrent CPU access to the BOs in question? > and reverting this commit solves the problem. I hope we can find a better solution. -- Earthling Michel Dänzer | http://www.amd.com Libre software enthusiast | Mesa and X developer _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/dri-devel
