All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Don't use WaGsvRC0ResidenncyMethod on chv
Date: Fri, 29 Aug 2014 16:01:50 +0300	[thread overview]
Message-ID: <20140829130150.GX4193@intel.com> (raw)
In-Reply-To: <20140829125104.GH3557@nuc-i3427.alporthouse.com>

On Fri, Aug 29, 2014 at 01:51:04PM +0100, Chris Wilson wrote:
> On Fri, Aug 29, 2014 at 03:09:49PM +0300, Ville Syrjälä wrote:
> > On Fri, Aug 29, 2014 at 12:21:27PM +0100, Chris Wilson wrote:
> > > On Fri, Aug 29, 2014 at 02:14:07PM +0300, ville.syrjala@linux.intel.com wrote:
> > > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > > 
> > > > WaGsvRC0ResidenncyMethod is for vlv, it doesn't deal with chv
> > > > appropriately (eg. doesn't limit rps values to even numbers).
> > > > 
> > > > Fix a typo in the w/a name while at it.
> > > 
> > > You could review my changes for the vlv manual calculations that would
> > > fix it for chv as well...
> > 
> > IIRC I glanced at them but there was too much noise in some of the
> > patches for my poor brain so I gave up.
> 
> Could you clarify whether you mean WaGsvRC0ResidenncyMethod is only
> intended for vlv (fixed for chv), or whether just the implementation is
> currently only for chv.

At least the w/a isn't listed for chv currently.

> 
> If the former, and the code is no longer required,
> Reviewed-by: Chris Wilson <chris@chris-wilson.o.uk>
> -Chris
> 
> -- 
> Chris Wilson, Intel Open Source Technology Centre

-- 
Ville Syrjälä
Intel OTC

  reply	other threads:[~2014-08-29 13:01 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-29 11:14 [PATCH] drm/i915: Don't use WaGsvRC0ResidenncyMethod on chv ville.syrjala
2014-08-29 11:21 ` Chris Wilson
2014-08-29 12:09   ` Ville Syrjälä
2014-08-29 12:51     ` Chris Wilson
2014-08-29 13:01       ` Ville Syrjälä [this message]
2014-09-02  2:35   ` Deepak S
2014-08-31  6:18 ` Deepak S

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=20140829130150.GX4193@intel.com \
    --to=ville.syrjala@linux.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 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.