From: Ben Widawsky <ben@bwidawsk.net>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org, miku@iki.fi
Subject: Re: [PATCH 1/7] drm/i915: add struct i915_ctx_hang_stats
Date: Wed, 12 Jun 2013 14:13:26 -0700 [thread overview]
Message-ID: <20130612211325.GA17916@bwidawsk.net> (raw)
In-Reply-To: <1371029734-10355-1-git-send-email-mika.kuoppala@intel.com>
On Wed, Jun 12, 2013 at 12:35:28PM +0300, Mika Kuoppala wrote:
> To count context losses, add struct i915_ctx_hang_stats for
> both i915_hw_context and drm_i915_file_private.
> drm_i915_file_private is used when there is no context.
>
> v2: renamed and cleaned up the struct (Chris Wilson, Ian Romanick)
>
> Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
>
I don't have time to do a proper review before Daniel wants to merge
these, and Chris has already reviewed it.
1-6 are:
Acked-by: Ben Widawsky <ben@bwidawsk.net>
I don't really like the behavior of 7. At least, I'd like to make it
something that can be disabled via debugfs, sysfs, or module parameter.
(I'd very much prefer it to be opt-in also). TBH , I only read it very
fast, and I'm not horribly opposed to it, just a bunch of complexity for
IMO little gain. Presumably the problem it's trying to solve should be
fixed with a fix to ddx, mesa, libva, client, whatever. In the embedded
case, the same thing applies. Banning the guilty doesn't make the user
experience any better. So the only thing I see is DoS, but we've never
*really* made that our priority anyway, so, meh.
--
Ben Widawsky, Intel Open Source Technology Center
next prev parent reply other threads:[~2013-06-12 21:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 9:35 [PATCH 1/7] drm/i915: add struct i915_ctx_hang_stats Mika Kuoppala
2013-06-12 9:35 ` [PATCH 2/7] drm/i915: add i915_gem_context_get_hang_stats() Mika Kuoppala
2013-06-12 9:35 ` [PATCH 3/7] drm/i915: change i915_add_request to macro Mika Kuoppala
2013-06-12 9:35 ` [PATCH 4/7] drm/i915: add batch bo to i915_add_request() Mika Kuoppala
2013-06-12 10:09 ` Chris Wilson
2013-06-12 12:01 ` Mika Kuoppala
2013-06-12 9:35 ` [PATCH 5/7] drm/i915: store ring hangcheck action Mika Kuoppala
2013-06-12 9:35 ` [PATCH 6/7] drm/i915: find guilty batch buffer on ring resets Mika Kuoppala
2013-06-12 10:17 ` Chris Wilson
2013-06-12 12:13 ` Mika Kuoppala
2013-06-12 9:35 ` [PATCH 7/7] drm/i915: refuse to submit more batchbuffers from guilty context Mika Kuoppala
2013-06-12 10:33 ` [PATCH 1/7] drm/i915: add struct i915_ctx_hang_stats Chris Wilson
2013-06-12 21:13 ` Ben Widawsky [this message]
2013-06-12 22:44 ` Chris Wilson
2013-06-13 9:53 ` Daniel Vetter
2013-06-13 20:59 ` Daniel Vetter
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=20130612211325.GA17916@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@linux.intel.com \
--cc=miku@iki.fi \
/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