public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Mika Kuoppala <mika.kuoppala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org,
	Kenneth Graunke <kenneth@whitecape.org>
Subject: Re: [PATCH] drm/i915: Add process identifier to requests
Date: Thu, 12 Feb 2015 10:35:09 +0100	[thread overview]
Message-ID: <20150212093509.GZ24485@phenom.ffwll.local> (raw)
In-Reply-To: <20150212085120.GC2749@nuc-i3427.alporthouse.com>

On Thu, Feb 12, 2015 at 08:51:20AM +0000, Chris Wilson wrote:
> On Thu, Feb 12, 2015 at 10:26:02AM +0200, Mika Kuoppala wrote:
> > We use the pid of the process which opened our device when
> > we track which was the culprit of the gpu hang. But as that
> > file descriptor might get inherited, we might blame the
> > wrong process when we record the error state.
> > 
> > Track process identifiers in requests to always find
> > the correct offender.
> > 
> > v2: Track only user processes (Chris)
> > 
> > Cc: Kenneth Graunke <kenneth@whitecape.org>
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
> > ---
> > @@ -2572,6 +2574,9 @@ static void i915_gem_free_request(struct drm_i915_gem_request *request)
> >  	list_del(&request->list);
> >  	i915_gem_request_remove_from_client(request);
> >  
> > +	if (request->pid)
> 
> put_pid() does the NULL check itself, might as well take advantage of
> that.

Done while merging.
> 
> > +		put_pid(request->pid);
> > +
> >  	i915_gem_request_unreference(request);
> >  }
> 
> Otherwise,
> Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>

Queued for -next, thanks for the patch.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2015-02-12  9:34 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-11 14:50 [PATCH] drm/i915: Add process identifier to requests Mika Kuoppala
2015-02-11 15:29 ` Chris Wilson
2015-02-12  8:26   ` Mika Kuoppala
2015-02-12  8:51     ` Chris Wilson
2015-02-12  9:35       ` Daniel Vetter [this message]
2015-02-13 10:41     ` shuang.he
2015-02-13 16:24   ` John Harrison
2015-02-13 16:54     ` Chris Wilson
2015-02-12  6:49 ` shuang.he

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20150212093509.GZ24485@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=kenneth@whitecape.org \
    --cc=mika.kuoppala@linux.intel.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox