diff options
author | 2014-08-27 15:22:01 +0200 | |
---|---|---|
committer | 2014-08-27 17:42:13 -0400 | |
commit | 3c0363891c0fa5d17b683b758bff0d81fa6a9775 (patch) | |
tree | 337fd0eafeee1d0fcab6f3181ee28b7d2b7eb7c0 /tools/perf/scripts/python/call-graph-from-postgresql.py | |
parent | drm/radeon: drop RADEON_FENCE_SIGNALED_SEQ v2 (diff) | |
download | linux-dev-3c0363891c0fa5d17b683b758bff0d81fa6a9775.tar.xz linux-dev-3c0363891c0fa5d17b683b758bff0d81fa6a9775.zip |
drm/radeon: drop doing resets in a work item
Blocking completely innocent processes with a GPU reset is
a pretty bad idea. Just set needs_reset and let the next
command submission or fence wait do the job.
Signed-off-by: Christian König <christian.koenig@amd.com>
Reviewed-by: Maarten Lankhorst <maarten.lankhorst@canonical.com>
Signed-off-by: Alex Deucher <alexander.deucher@amd.com>
Diffstat (limited to 'tools/perf/scripts/python/call-graph-from-postgresql.py')
0 files changed, 0 insertions, 0 deletions