Hi,
On pe, 2016-03-11 at 16:38 +, John Harrison wrote:
> The intention of the state dump code is not really for it to be a user
> accessible debugfs entry (although one of the later patches does add a
> debugfs interface). It is more intended for debugging lock ups and
> unexpected behaviou
The intention of the state dump code is not really for it to be a user
accessible debugfs entry (although one of the later patches does add a
debugfs interface). It is more intended for debugging lock ups and
unexpected behaviour by adding a dump function call to whatever WARN_ON
or similar is
Hi,
On to, 2016-02-18 at 14:27 +, john.c.harri...@intel.com wrote:
> From: John Harrison
>
> When debugging batch buffer submission issues, it is useful to be able
> to see what the current state of the scheduler is. This change adds
> functions for decoding the internal scheduler state and
From: John Harrison
When debugging batch buffer submission issues, it is useful to be able
to see what the current state of the scheduler is. This change adds
functions for decoding the internal scheduler state and reporting it.
v3: Updated a debug message with the new state_str() function.
v4:
