From: Chris Wilson <chris@chris-wilson.co.uk>
To: Ben Widawsky <benjamin.widawsky@intel.com>
Cc: Intel GFX <intel-gfx@lists.freedesktop.org>,
Ben Widawsky <ben@bwidawsk.net>
Subject: Re: [PATCH 6/7] drm/i915: Add some more registers to error state
Date: Tue, 28 Jan 2014 11:43:41 +0000 [thread overview]
Message-ID: <20140128114341.GM2508@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <1390892826-26973-6-git-send-email-benjamin.widawsky@intel.com>
On Mon, Jan 27, 2014 at 11:07:05PM -0800, Ben Widawsky wrote:
> Chris:
> Do we also want to capture?
> GAC_ECO_BITS /* gen6,7 */
> GAM_ECOCHK /* gen6,7 */
> GAB_CTL /* gen6 */
> GFX_MODE /* gen6 */
>
> Requested-by: Chris Wilson <chris@chris-wilson.co.uk>
> Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2014-01-28 11:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 7:07 [PATCH 1/7] [v2] drm/i915: Create a USES_PPGTT macro Ben Widawsky
2014-01-28 7:07 ` [PATCH 2/7] drm/i915: Extract register state error capture Ben Widawsky
2014-01-28 11:33 ` Chris Wilson
2014-01-28 7:07 ` [PATCH 3/7] drm/i915: Logically reorder error register capture Ben Widawsky
2014-01-28 11:37 ` Chris Wilson
2014-01-28 7:07 ` [PATCH 4/7] drm/i915: Reorder struct members Ben Widawsky
2014-01-28 11:39 ` Chris Wilson
2014-01-28 7:07 ` [PATCH 5/7] drm/i915: Move per ring error state to ring_error Ben Widawsky
2014-01-28 11:42 ` Chris Wilson
2014-01-28 7:07 ` [PATCH 6/7] drm/i915: Add some more registers to error state Ben Widawsky
2014-01-28 11:43 ` Chris Wilson [this message]
2014-01-28 7:07 ` [PATCH 7/7] [v2] drm/i915: Capture PPGTT info on error capture Ben Widawsky
2014-01-28 11:47 ` Chris Wilson
2014-01-28 8:14 ` [PATCH 1/7] [v2] drm/i915: Create a USES_PPGTT macro 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=20140128114341.GM2508@nuc-i3427.alporthouse.com \
--to=chris@chris-wilson.co.uk \
--cc=ben@bwidawsk.net \
--cc=benjamin.widawsky@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.