All of lore.kernel.org
 help / color / mirror / Atom feed
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 5/7] drm/i915: Move per ring error state to ring_error
Date: Tue, 28 Jan 2014 11:42:37 +0000	[thread overview]
Message-ID: <20140128114237.GL2508@nuc-i3427.alporthouse.com> (raw)
In-Reply-To: <1390892826-26973-5-git-send-email-benjamin.widawsky@intel.com>

On Mon, Jan 27, 2014 at 11:07:04PM -0800, Ben Widawsky wrote:
> Signed-off-by: Ben Widawsky <ben@bwidawsk.net>
> ---
>  drivers/gpu/drm/i915/i915_drv.h       |  62 +++++++--------
>  drivers/gpu/drm/i915/i915_gpu_error.c | 137 +++++++++++++++++-----------------
>  2 files changed, 99 insertions(+), 100 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> index bb53de5..defdb00 100644
> --- a/drivers/gpu/drm/i915/i915_drv.h
> +++ b/drivers/gpu/drm/i915/i915_drv.h
> @@ -313,49 +313,49 @@ struct drm_i915_error_state {
>  	struct intel_overlay_error_state *overlay;
>  	struct intel_display_error_state *display;
>  
> -	/* Per ring register state
> -	 * TODO: Move these to per ring */
> -	u32 tail[I915_NUM_RINGS];
> -	u32 head[I915_NUM_RINGS];
> -	u32 ctl[I915_NUM_RINGS];
> -	u32 hws[I915_NUM_RINGS];
> -	u32 ipeir[I915_NUM_RINGS];
> -	u32 ipehr[I915_NUM_RINGS];
> -	u32 instdone[I915_NUM_RINGS];
> -	u32 acthd[I915_NUM_RINGS];
> -	u32 bbstate[I915_NUM_RINGS];
> -	u32 instpm[I915_NUM_RINGS];
> -	u32 instps[I915_NUM_RINGS];
> -	u32 seqno[I915_NUM_RINGS];
> -	u64 bbaddr[I915_NUM_RINGS];
> -	u32 fault_reg[I915_NUM_RINGS];
> -	u32 faddr[I915_NUM_RINGS];
> -	u32 rc_psmi[I915_NUM_RINGS]; /* sleep state */
> -	u32 semaphore_mboxes[I915_NUM_RINGS][I915_NUM_RINGS - 1];
> -
> -	/* Software tracked state */
> -	bool waiting[I915_NUM_RINGS];
> -	int hangcheck_score[I915_NUM_RINGS];
> -	enum intel_ring_hangcheck_action hangcheck_action[I915_NUM_RINGS];
> -
> -	/* our own tracking of ring head and tail */
> -	u32 cpu_ring_head[I915_NUM_RINGS];
> -	u32 cpu_ring_tail[I915_NUM_RINGS];
> -	u32 semaphore_seqno[I915_NUM_RINGS][I915_NUM_RINGS - 1];
> -
>  	struct drm_i915_error_ring {
>  		bool valid;
> +		/* Software tracked state */
> +		bool waiting;

Looks like we have some bools to coallesce! :)

> +		int hangcheck_score;
> +		enum intel_ring_hangcheck_action hangcheck_action;
> +
> +		/* Register state */
> +		u32 tail;
> +		u32 head;
> +		u32 ctl;
> +		u32 ipeir;
> +		u32 ipehr;
> +		u32 instdone;
> +		u32 acthd;
> +		u32 bbstate;
> +		u32 instpm;
> +		u32 instps;
> +		u32 seqno;
> +		u64 bbaddr;
> +		u32 fault_reg;
> +		u32 faddr;
> +		u32 rc_psmi; /* sleep state */
> +		u32 semaphore_mboxes[I915_NUM_RINGS - 1];
> +
> +		/* our own tracking of ring head and tail */
> +		u32 cpu_ring_head;
> +		u32 cpu_ring_tail;
> +
> +		u32 semaphore_seqno[I915_NUM_RINGS - 1];
> +
>  		struct drm_i915_error_object {
>  			int page_count;
>  			u32 gtt_offset;
>  			u32 *pages[0];
>  		} *ringbuffer, *batchbuffer, *ctx, *hws;
> +
> +		int num_requests;

This feels a little odd - we split up a set of pointers with a int+hole.

>  		struct drm_i915_error_request {
>  			long jiffies;
>  			u32 seqno;
>  			u32 tail;
>  		} *requests;
> -		int num_requests;
>  	} ring[I915_NUM_RINGS];
>  
>  	struct drm_i915_error_buffer {

The code cleanup is well worth it,
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  reply	other threads:[~2014-01-28 11:42 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 [this message]
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
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=20140128114237.GL2508@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.