From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Daniel Vetter <daniel@ffwll.ch>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: Increase max fence pitch limit to 256KB on IVB+
Date: Tue, 9 Apr 2013 15:03:28 +0300 [thread overview]
Message-ID: <20130409120328.GP4469@intel.com> (raw)
In-Reply-To: <20130409115401.GV2228@phenom.ffwll.local>
On Tue, Apr 09, 2013 at 01:54:01PM +0200, Daniel Vetter wrote:
> On Tue, Apr 09, 2013 at 11:45:05AM +0300, ville.syrjala@linux.intel.com wrote:
> > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> >
> > BSpec contains several scattered notes which state that the maximum
> > fence stride was increased to 256KB on IVB.
> >
> > Testing on real hardware agrees.
> >
> > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/i915_gem_tiling.c | 9 ++++++---
> > drivers/gpu/drm/i915/i915_reg.h | 1 +
> > 2 files changed, 7 insertions(+), 3 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/i915_gem_tiling.c b/drivers/gpu/drm/i915/i915_gem_tiling.c
> > index c807eb9..139d17d 100644
> > --- a/drivers/gpu/drm/i915/i915_gem_tiling.c
> > +++ b/drivers/gpu/drm/i915/i915_gem_tiling.c
> > @@ -217,9 +217,12 @@ i915_tiling_ok(struct drm_device *dev, int stride, int size, int tiling_mode)
> > tile_width = 512;
> >
> > /* check maximum stride & object size */
> > - if (INTEL_INFO(dev)->gen >= 4) {
> > - /* i965 stores the end address of the gtt mapping in the fence
> > - * reg, so dont bother to check the size */
> > + /* i965+ stores the end address of the gtt mapping in the fence
> > + * reg, so dont bother to check the size */
> > + if (INTEL_INFO(dev)->gen >= 7) {
>
> I've thought that his does not apply to vlv? Or has that now changed?
The docs are telling me that VLV also has 256KB max stride.
> -Daniel
>
> > + if (stride / 128 > GEN7_FENCE_MAX_PITCH_VAL)
> > + return false;
> > + } else if (INTEL_INFO(dev)->gen >= 4) {
> > if (stride / 128 > I965_FENCE_MAX_PITCH_VAL)
> > return false;
> > } else {
> > diff --git a/drivers/gpu/drm/i915/i915_reg.h b/drivers/gpu/drm/i915/i915_reg.h
> > index 0e4b7fb..ec4e054 100644
> > --- a/drivers/gpu/drm/i915/i915_reg.h
> > +++ b/drivers/gpu/drm/i915/i915_reg.h
> > @@ -424,6 +424,7 @@
> >
> > #define FENCE_REG_SANDYBRIDGE_0 0x100000
> > #define SANDYBRIDGE_FENCE_PITCH_SHIFT 32
> > +#define GEN7_FENCE_MAX_PITCH_VAL 0x0800
> >
> > /* control register for cpu gtt access */
> > #define TILECTL 0x101000
> > --
> > 1.8.1.5
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> +41 (0) 79 365 57 48 - http://blog.ffwll.ch
--
Ville Syrjälä
Intel OTC
next prev parent reply other threads:[~2013-04-09 12:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 8:45 [PATCH 1/2] drm/i915: IVB/HSW have 32 fence register ville.syrjala
2013-04-09 8:45 ` [PATCH 2/2] drm/i915: Increase max fence pitch limit to 256KB on IVB+ ville.syrjala
2013-04-09 11:54 ` Daniel Vetter
2013-04-09 12:03 ` Ville Syrjälä [this message]
2013-04-09 18:16 ` Daniel Vetter
2013-04-09 10:02 ` [PATCH v2] drm/i915: IVB/HSW have 32 fence register ville.syrjala
2013-04-11 18:23 ` 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=20130409120328.GP4469@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=daniel@ffwll.ch \
--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.