[PATCH] drm: Include task->name and master status in debugfs clients info

2014-09-02 Thread Chris Wilson
Showing who is the current master is useful for trying to decypher errors when trying to acquire master (e.g. a race with X taking over from plymouth). By including the process name as well as the pid simplifies the task of grabbing enough information remotely at the point of error. v2: Add the co

[PATCH] drm: Include task->name and master status in debugfs clients info

2014-09-01 Thread David Herrmann
Hi On Mon, Sep 1, 2014 at 4:19 PM, Chris Wilson wrote: > On Mon, Sep 01, 2014 at 04:11:43PM +0200, David Herrmann wrote: >> Hi >> >> On Sat, Aug 9, 2014 at 8:22 AM, Chris Wilson >> wrote: >> > Showing who is the current master is useful for trying to decypher >> > errors when trying to acquire

[PATCH] drm: Include task->name and master status in debugfs clients info

2014-09-01 Thread David Herrmann
Hi On Sat, Aug 9, 2014 at 8:22 AM, Chris Wilson wrote: > Showing who is the current master is useful for trying to decypher > errors when trying to acquire master (e.g. a race with X taking over > from plymouth). By including the process name as well as the pid > simplifies the task of grabbing

[PATCH] drm: Include task->name and master status in debugfs clients info

2014-09-01 Thread Chris Wilson
On Mon, Sep 01, 2014 at 04:11:43PM +0200, David Herrmann wrote: > Hi > > On Sat, Aug 9, 2014 at 8:22 AM, Chris Wilson > wrote: > > Showing who is the current master is useful for trying to decypher > > errors when trying to acquire master (e.g. a race with X taking over > > from plymouth). By in

[PATCH] drm: Include task->name and master status in debugfs clients info

2014-08-09 Thread Chris Wilson
Showing who is the current master is useful for trying to decypher errors when trying to acquire master (e.g. a race with X taking over from plymouth). By including the process name as well as the pid simplifies the task of grabbing enough information remotely at the point of error. Signed-off-by: