diff options
| author | Evan Quan <[email protected]> | 2018-03-15 09:49:01 +0800 |
|---|---|---|
| committer | Alex Deucher <[email protected]> | 2018-03-21 14:36:57 -0500 |
| commit | f0c2b16ba84a0b8b960a6d442496ce2d2e6bfa99 (patch) | |
| tree | c8320a4044e341eda7bdfa60b2f9a047ae9ba5ca /tools/perf/util/scripting-engines/trace-event-python.c | |
| parent | dc53d543fcb4fdcd836fffaf0b12d3b1b69cde62 (diff) | |
drm/amdgpu: no job timeout setting on compute queues
Under some heavy computing environment(e.g. dgemm test), it
takes the asic over 10+ seconds to finish the dispatched job
which will trigger the timeout.
It's quite confusing although it does not seem to bring any
real problems. As a quick workround, we choose to not enfoce
the timeout setting on compute queues.
Signed-off-by: Evan Quan <[email protected]>
Acked-by: Alex Deucher <[email protected]>
Reviewed-by: Christian König <[email protected]>
Signed-off-by: Alex Deucher <[email protected]>
Diffstat (limited to 'tools/perf/util/scripting-engines/trace-event-python.c')
0 files changed, 0 insertions, 0 deletions