trace: don't trace resource_destroy
authorMarek Olšák <marek.olsak@amd.com>
Sun, 16 Apr 2017 18:09:03 +0000 (20:09 +0200)
committerMarek Olšák <marek.olsak@amd.com>
Tue, 25 Apr 2017 20:39:31 +0000 (22:39 +0200)
commit231dfa5a029f99d8bb2d4b0f34915bbc58458f93
treee754bd736b395ce4f03647165b0de8158f79196a
parent2c1ec23a0618b93cf0f5ae29aac27bb2c4a5e18c
trace: don't trace resource_destroy

due to the lack of pipe_resource wrapping, we can get this call from inside
of driver calls, which would try to lock an already-locked mutex.

Reviewed-by: Nicolai Hähnle <nicolai.haehnle@amd.com>
src/gallium/drivers/trace/tr_screen.c