[PATCH] drm/amdgpu: support gpu recovery tests on compute rings
Michel Dänzer
michel at daenzer.net
Fri Apr 26 08:35:24 UTC 2019
On 2019-04-26 10:20 a.m., Quan, Evan wrote:
> My concern is there is already one module parameter "lockup_timeout".
> parm: lockup_timeout:GPU lockup timeout in ms > 0 (default 10000) (int)
>
> Adding one more "timeout" seems redundant.
> And that will makes the description of "lockup_timeout"(seems working for all jobs) does not match its real effect(affect only non-compute jobs).
>
> A better way is to rename "lockup_timeout" to "non-compute lockup_timeout". But I do not think we can change existing module parameter. Right?
Right. Also, there are already too many amdgpu module parameters, we
should try to remove some rather than adding new ones for every little
thing that could be tweaked. :)
One possibility might be to optionally allow passing multiple values to
lockup_timeout, e.g.
amdgpu.lockup_timeout=10000,0
The first value would need to have the same meaning as now for backwards
compatibility.
--
Earthling Michel Dänzer | https://www.amd.com
Libre software enthusiast | Mesa and X developer
More information about the amd-gfx
mailing list