We only want to scare the user away from causing a GPU stall for mapping a busy bo. The time taken to instantiate the set of pages for a buffer and their mmapping is unavoidable and flagging idle bo as being busy is "crying wolf".
Reported-by: Tvrtko Ursulin <[email protected]> Cc: Kenneth Graunke <[email protected]> --- src/mesa/drivers/dri/i965/brw_bufmgr.c | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/src/mesa/drivers/dri/i965/brw_bufmgr.c b/src/mesa/drivers/dri/i965/brw_bufmgr.c index f12a3786eb..0db54fa3d1 100644 --- a/src/mesa/drivers/dri/i965/brw_bufmgr.c +++ b/src/mesa/drivers/dri/i965/brw_bufmgr.c @@ -734,11 +734,12 @@ bo_wait_with_stall_warning(struct brw_context *brw, struct brw_bo *bo, const char *action) { - double elapsed = unlikely(brw && brw->perf_debug) ? -get_time() : 0.0; + bool busy = brw && brw->perf_debug && !bo->idle; + double elapsed = unlikely(busy) ? -get_time() : 0.0; brw_bo_wait_rendering(bo); - if (unlikely(brw && brw->perf_debug)) { + if (unlikely(busy)) { elapsed += get_time(); if (elapsed > 1e-5) /* 0.01ms */ perf_debug("%s a busy \"%s\" BO stalled and took %.03f ms.\n", -- 2.15.0.rc1 _______________________________________________ mesa-dev mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/mesa-dev
