On ti, 2016-09-20 at 09:29 +0100, Chris Wilson wrote:
> We currently capture the GPU state after we detect a hang. This is vital
> for us to both triage and debug hangs in the wild (post-mortem
> debugging). However, it comes at the cost of running some potentially
> dangerous code (since it has to make very few assumption about the state
> of the driver) that is quite resource intensive.
I might have included more, like the member in the module parameter
structure, but I see you deliberately left them out.
Reviewed-by: Joonas Lahtinen <joonas.lahti...@linux.intel.com>
Open Source Technology Center
Intel-gfx mailing list