All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
Cc: tomi.p.sarvela@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2] drm/i915: Support more QGV points
Date: Mon, 25 Nov 2019 17:31:43 +0200	[thread overview]
Message-ID: <20191125153143.GX1208@intel.com> (raw)
In-Reply-To: <20191122141049.25608-1-stanislav.lisovskiy@intel.com>

On Fri, Nov 22, 2019 at 04:10:49PM +0200, Stanislav Lisovskiy wrote:
> According to BSpec 53998, there is a mask of
> max 8 SAGV/QGV points we need to support.
> 
> Bumping this up to keep the CI happy(currently
> preventing tests to run), until all SAGV
> changes land.
> 
> Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=112189
> Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_bw.c | 22 +++++++++++++++++-----
>  drivers/gpu/drm/i915/i915_drv.h         |  6 +++++-
>  2 files changed, 22 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_bw.c b/drivers/gpu/drm/i915/display/intel_bw.c
> index 86e75e858008..d1b805b30177 100644
> --- a/drivers/gpu/drm/i915/display/intel_bw.c
> +++ b/drivers/gpu/drm/i915/display/intel_bw.c
> @@ -15,7 +15,7 @@ struct intel_qgv_point {
>  };
>  
>  struct intel_qgv_info {
> -	struct intel_qgv_point points[3];
> +	struct intel_qgv_point points[I915_NUM_SAGV_POINTS];
>  	u8 num_points;
>  	u8 num_channels;
>  	u8 t_bl;
> @@ -276,15 +276,27 @@ void intel_bw_init_hw(struct drm_i915_private *dev_priv)
>  static unsigned int intel_max_data_rate(struct drm_i915_private *dev_priv,
>  					int num_planes)
>  {
> -	if (INTEL_GEN(dev_priv) >= 11)
> +	if (INTEL_GEN(dev_priv) >= 11) {
> +		/*
> +		 * Any bw group has same amount of QGV points
> +		 */
> +		const struct intel_bw_info *bi =
> +			&dev_priv->max_bw[0];
> +		unsigned int min_bw = UINT_MAX;
> +		int i;
> +
>  		/*
>  		 * FIXME with SAGV disabled maybe we can assume
>  		 * point 1 will always be used? Seems to match
>  		 * the behaviour observed in the wild.
>  		 */
> -		return min3(icl_max_bw(dev_priv, num_planes, 0),
> -			    icl_max_bw(dev_priv, num_planes, 1),
> -			    icl_max_bw(dev_priv, num_planes, 2));
> +		for (i = 0; i < bi->num_qgv_points; i++) {
> +			unsigned int bw = icl_max_bw(dev_priv, num_planes, i);
> +
> +			min_bw = min(bw, min_bw);
> +		}
> +		return min_bw;
> +	}
>  	else
>  		return UINT_MAX;
>  }
> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> index fdae5a919bc8..d45a9ffaed4f 100644
> --- a/drivers/gpu/drm/i915/i915_drv.h
> +++ b/drivers/gpu/drm/i915/i915_drv.h
> @@ -621,6 +621,9 @@ struct i915_gem_mm {
>  
>  #define I915_ENGINE_WEDGED_TIMEOUT  (60 * HZ)  /* Reset but no recovery? */
>  
> +/* BSpec precisely defines this */
> +#define I915_NUM_SAGV_POINTS 8

I think everything else talks about "QGV points" rather
than "SAGV points" now? Would be nice to be consistent.

Apart from that
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

> +
>  struct ddi_vbt_port_info {
>  	/* Non-NULL if port present. */
>  	const struct child_device_config *child;
> @@ -1232,7 +1235,8 @@ struct drm_i915_private {
>  	} dram_info;
>  
>  	struct intel_bw_info {
> -		unsigned int deratedbw[3]; /* for each QGV point */
> +		/* for each QGV point */
> +		unsigned int deratedbw[I915_NUM_SAGV_POINTS];
>  		u8 num_qgv_points;
>  		u8 num_planes;
>  	} max_bw[6];
> -- 
> 2.17.1

-- 
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

WARNING: multiple messages have this Message-ID (diff)
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
Cc: tomi.p.sarvela@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2] drm/i915: Support more QGV points
Date: Mon, 25 Nov 2019 17:31:43 +0200	[thread overview]
Message-ID: <20191125153143.GX1208@intel.com> (raw)
Message-ID: <20191125153143.7Hej4v5U8hnQXIK05gc4I-XA5RWZwQE-TyN57DmiocQ@z> (raw)
In-Reply-To: <20191122141049.25608-1-stanislav.lisovskiy@intel.com>

On Fri, Nov 22, 2019 at 04:10:49PM +0200, Stanislav Lisovskiy wrote:
> According to BSpec 53998, there is a mask of
> max 8 SAGV/QGV points we need to support.
> 
> Bumping this up to keep the CI happy(currently
> preventing tests to run), until all SAGV
> changes land.
> 
> Fixes: https://bugs.freedesktop.org/show_bug.cgi?id=112189
> Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_bw.c | 22 +++++++++++++++++-----
>  drivers/gpu/drm/i915/i915_drv.h         |  6 +++++-
>  2 files changed, 22 insertions(+), 6 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/display/intel_bw.c b/drivers/gpu/drm/i915/display/intel_bw.c
> index 86e75e858008..d1b805b30177 100644
> --- a/drivers/gpu/drm/i915/display/intel_bw.c
> +++ b/drivers/gpu/drm/i915/display/intel_bw.c
> @@ -15,7 +15,7 @@ struct intel_qgv_point {
>  };
>  
>  struct intel_qgv_info {
> -	struct intel_qgv_point points[3];
> +	struct intel_qgv_point points[I915_NUM_SAGV_POINTS];
>  	u8 num_points;
>  	u8 num_channels;
>  	u8 t_bl;
> @@ -276,15 +276,27 @@ void intel_bw_init_hw(struct drm_i915_private *dev_priv)
>  static unsigned int intel_max_data_rate(struct drm_i915_private *dev_priv,
>  					int num_planes)
>  {
> -	if (INTEL_GEN(dev_priv) >= 11)
> +	if (INTEL_GEN(dev_priv) >= 11) {
> +		/*
> +		 * Any bw group has same amount of QGV points
> +		 */
> +		const struct intel_bw_info *bi =
> +			&dev_priv->max_bw[0];
> +		unsigned int min_bw = UINT_MAX;
> +		int i;
> +
>  		/*
>  		 * FIXME with SAGV disabled maybe we can assume
>  		 * point 1 will always be used? Seems to match
>  		 * the behaviour observed in the wild.
>  		 */
> -		return min3(icl_max_bw(dev_priv, num_planes, 0),
> -			    icl_max_bw(dev_priv, num_planes, 1),
> -			    icl_max_bw(dev_priv, num_planes, 2));
> +		for (i = 0; i < bi->num_qgv_points; i++) {
> +			unsigned int bw = icl_max_bw(dev_priv, num_planes, i);
> +
> +			min_bw = min(bw, min_bw);
> +		}
> +		return min_bw;
> +	}
>  	else
>  		return UINT_MAX;
>  }
> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> index fdae5a919bc8..d45a9ffaed4f 100644
> --- a/drivers/gpu/drm/i915/i915_drv.h
> +++ b/drivers/gpu/drm/i915/i915_drv.h
> @@ -621,6 +621,9 @@ struct i915_gem_mm {
>  
>  #define I915_ENGINE_WEDGED_TIMEOUT  (60 * HZ)  /* Reset but no recovery? */
>  
> +/* BSpec precisely defines this */
> +#define I915_NUM_SAGV_POINTS 8

I think everything else talks about "QGV points" rather
than "SAGV points" now? Would be nice to be consistent.

Apart from that
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

> +
>  struct ddi_vbt_port_info {
>  	/* Non-NULL if port present. */
>  	const struct child_device_config *child;
> @@ -1232,7 +1235,8 @@ struct drm_i915_private {
>  	} dram_info;
>  
>  	struct intel_bw_info {
> -		unsigned int deratedbw[3]; /* for each QGV point */
> +		/* for each QGV point */
> +		unsigned int deratedbw[I915_NUM_SAGV_POINTS];
>  		u8 num_qgv_points;
>  		u8 num_planes;
>  	} max_bw[6];
> -- 
> 2.17.1

-- 
Ville Syrjälä
Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  parent reply	other threads:[~2019-11-25 15:31 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-22 14:10 [PATCH v2] drm/i915: Support more QGV points Stanislav Lisovskiy
2019-11-22 14:10 ` [Intel-gfx] " Stanislav Lisovskiy
2019-11-22 14:45 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Support more QGV points (rev3) Patchwork
2019-11-22 14:45   ` [Intel-gfx] " Patchwork
2019-11-22 15:07 ` ✓ Fi.CI.BAT: success " Patchwork
2019-11-22 15:07   ` [Intel-gfx] " Patchwork
2019-11-23 23:10 ` ✓ Fi.CI.IGT: " Patchwork
2019-11-23 23:10   ` [Intel-gfx] " Patchwork
2019-11-25 15:31 ` Ville Syrjälä [this message]
2019-11-25 15:31   ` [Intel-gfx] [PATCH v2] drm/i915: Support more QGV points Ville Syrjälä
2019-11-25 15:55   ` Lisovskiy, Stanislav
2019-11-25 15:55     ` [Intel-gfx] " Lisovskiy, Stanislav
2019-11-25 16:03     ` Saarinen, Jani
2019-11-25 16:03       ` [Intel-gfx] " Saarinen, Jani
2019-11-25 16:08       ` Lisovskiy, Stanislav
2019-11-25 16:08         ` [Intel-gfx] " Lisovskiy, Stanislav
  -- strict thread matches above, loose matches on Subject: below --
2019-11-22 14:09 Stanislav Lisovskiy

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=20191125153143.GX1208@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=stanislav.lisovskiy@intel.com \
    --cc=tomi.p.sarvela@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 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.