From: Ben Widawsky <ben@bwidawsk.net>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Ben Widawsky <benjamin.widawsky@intel.com>,
Intel GFX <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH 4/5] drm/i915: Capture PPGTT info on error capture
Date: Sun, 26 Jan 2014 11:06:40 -0800 [thread overview]
Message-ID: <20140126190640.GF894@bwidawsk.net> (raw)
In-Reply-To: <20140126114222.GE23557@nuc-i3427.alporthouse.com>
On Sun, Jan 26, 2014 at 11:42:22AM +0000, Chris Wilson wrote:
> On Fri, Jan 24, 2014 at 06:17:44PM -0800, Ben Widawsky wrote:
> > Cc: Chris Wilson <chris@chris-wilson.co.uk>
> > Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
> > ---
> > drivers/gpu/drm/i915/i915_drv.h | 7 ++++++
> > drivers/gpu/drm/i915/i915_gpu_error.c | 41 +++++++++++++++++++++++++++++++++++
> > 2 files changed, 48 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> > index 6f68515..5105fd4 100644
> > --- a/drivers/gpu/drm/i915/i915_drv.h
> > +++ b/drivers/gpu/drm/i915/i915_drv.h
> > @@ -359,6 +359,13 @@ struct drm_i915_error_state {
> > s32 ring:4;
> > u32 cache_level:3;
> > } **active_bo, **pinned_bo;
> > + struct drm_i915_vm_info {
> > + u32 gfx_mode;
> > + union {
> > + u64 pdp[4];
> > + u32 pp_dir_base;
> > + };
> > + } vm_info[I915_NUM_RINGS];
>
> Note for future janitorial work: let's coalesce all the per-ring
> information into the ring error struct.
>
> > u32 *active_bo_count, *pinned_bo_count;
>
> For instance, I thought active_bo was already being tracked per-ring.
> (Pinned bo is global since that exists more or less to make sure that
> our registers are pointing into pinned objects.)
>
> Do we also want to capture?
> GAC_ECO_BITS /* gen6,7 */
> GAM_ECOCHK /* gen6,7 */
> GAB_CTL /* gen6 */
> GFX_MODE /* gen6 */
>
> The rest looks good.
> -Chris
>
I agree. I was pretty unhappy too with how we've done things, but as
this information is immediately useful, I'd really like to not postpone.
Does "The rest looks good." mean reviewed-by?
--
Ben Widawsky, Intel Open Source Technology Center
next prev parent reply other threads:[~2014-01-26 19:06 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-25 2:17 [PATCH 1/5] drm/i915: Place the Global GTT VM first in the list of VM Ben Widawsky
2014-01-25 2:17 ` [PATCH 2/5] drm/i915: Print captured bo for all VM in error state Ben Widawsky
2014-01-25 2:17 ` [PATCH 3/5] drm/i915: Create a USES_PPGTT macro Ben Widawsky
2014-01-25 20:41 ` Daniel Vetter
2014-01-26 5:45 ` Ben Widawsky
2014-01-26 9:24 ` Daniel Vetter
2014-01-25 2:17 ` [PATCH 4/5] drm/i915: Capture PPGTT info on error capture Ben Widawsky
2014-01-26 11:42 ` Chris Wilson
2014-01-26 19:06 ` Ben Widawsky [this message]
2014-01-26 19:51 ` Chris Wilson
2014-01-25 2:17 ` [PATCH 5/5] drm/i915: Fix error capture on BYT/BDW Ben Widawsky
2014-01-26 11:47 ` Chris Wilson
2014-01-26 19:05 ` Ben Widawsky
2014-01-26 19:55 ` Chris Wilson
2014-01-26 21:47 ` Ben Widawsky
2014-01-27 13:45 ` Chris Wilson
2014-01-27 18:24 ` Ben Widawsky
2014-01-27 20:31 ` Ben Widawsky
2014-01-27 21:31 ` Chris Wilson
2014-01-27 21:54 ` Ben Widawsky
2014-01-25 8:32 ` [PATCH 1/5] drm/i915: Place the Global GTT VM first in the list of VM Kenneth Graunke
2014-01-25 20:48 ` Daniel Vetter
2014-01-25 21:31 ` Kenneth Graunke
2014-01-26 5:09 ` Ben Widawsky
2014-01-26 9:26 ` Daniel Vetter
2014-01-26 11:10 ` 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=20140126190640.GF894@bwidawsk.net \
--to=ben@bwidawsk.net \
--cc=benjamin.widawsky@intel.com \
--cc=chris@chris-wilson.co.uk \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox