diff options
author | Eric Anholt <[email protected]> | 2012-12-14 14:02:34 -0800 |
---|---|---|
committer | Eric Anholt <[email protected]> | 2012-12-14 15:05:10 -0800 |
commit | 1315f3b4b38cb569846389fe3080ffa8ac6946d9 (patch) | |
tree | c77ba3efbad0f0d798d617c9ff89f094e0943ce0 /src/mesa/drivers | |
parent | 81c247404a232d17e94ec1b435c0f2be47877778 (diff) |
i965: Make sure that the shader_time report at context destroy happens.
Otherwise, you end up with some report from within a second of context
destroy, which is now what you really want for testing the impact of
changes
Diffstat (limited to 'src/mesa/drivers')
-rw-r--r-- | src/mesa/drivers/dri/i965/brw_vtbl.c | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/src/mesa/drivers/dri/i965/brw_vtbl.c b/src/mesa/drivers/dri/i965/brw_vtbl.c index f2f0e7b9590..237ec1ef78a 100644 --- a/src/mesa/drivers/dri/i965/brw_vtbl.c +++ b/src/mesa/drivers/dri/i965/brw_vtbl.c @@ -71,6 +71,9 @@ static void brw_destroy_context( struct intel_context *intel ) struct brw_context *brw = brw_context(&intel->ctx); if (INTEL_DEBUG & DEBUG_SHADER_TIME) { + /* Force a report. */ + brw->shader_time.report_time = 0; + brw_collect_and_report_shader_time(brw); brw_destroy_shader_time(brw); } |