public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Daniel Vetter <daniel@ffwll.ch>
To: sourab.gupta@intel.com
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 0/6] Rendering Specific HW Workarounds for VLV
Date: Mon, 24 Mar 2014 10:35:09 +0100	[thread overview]
Message-ID: <20140324093509.GD26878@phenom.ffwll.local> (raw)
In-Reply-To: <1395643764-24353-1-git-send-email-sourab.gupta@intel.com>

On Mon, Mar 24, 2014 at 12:19:18PM +0530, sourab.gupta@intel.com wrote:
> From: Sourab Gupta <sourab.gupta@intel.com>
> 
> This patch series adds rendering specific HW workarounds for VLV platform.
> These patches leads to stable behavior on VLV, especially
> when playing 3D Apps, benchmarks.
> 
> Though, the patch set was submitter earlier, this new patch set is initiating
> a clean thread. We have addressed the comments on earlier patches and given
> the latest version of these patches in a single thread.
> 
> Akash Goel (6):
>   drm/i915/vlv: Added a rendering specific Hw WA
>     'WaTlbInvalidateStoreDataBefore'
>   drm/i915/vlv: Added a rendering specific Hw WA
>     'WaSendDummy3dPrimitveAfterSetContext'
>   drm/i915: Enabling the TLB invalidate bit in GFX Mode register
>   drm/i915/vlv: Remove the enabling of VS_TIMER_DISPATCH bit in MI MODE
>     reg
>   drm/i915/vlv:Implement WaDisable_RenderCache_OperationalFlush
>   drm/i915/vlv: Modified Implementation of WaDisableL3Bank2xClockGate

Thanks for resending. But your patches are missing the in-patch changelogs
completely, which makes reviewing them hard - I have no idea what was
discussed already and why we've reached certain conclusions. Can you
please dig out the changelogs from older resends (I remember v2/v3/v4 of
some of your patches) and add this again?

Also you missed e.g. Chris' tested-by on the tlb invalidation
optimization. And the commit message fails to state that you've only
tested this on vlv, but Chris has done the required testing on ivb/hsw.

Such details are important in case the patch breaks something in the
future.

One comment on one patch before I've noticed this, otherwise I think it's
better to wait for the resend.

Thanks.
> 
>  drivers/gpu/drm/i915/i915_gem_context.c | 65 ++++++++++++++++++++++++++++++++-
>  drivers/gpu/drm/i915/i915_reg.h         |  6 +++
>  drivers/gpu/drm/i915/intel_pm.c         | 13 ++++++-
>  drivers/gpu/drm/i915/intel_ringbuffer.c | 38 ++++++++++++++++++-
>  drivers/gpu/drm/i915/intel_ringbuffer.h |  1 +
>  5 files changed, 117 insertions(+), 6 deletions(-)
> 
> -- 
> 1.8.5.1
> 

-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch

  parent reply	other threads:[~2014-03-24  9:35 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-24  6:49 [PATCH 0/6] Rendering Specific HW Workarounds for VLV sourab.gupta
2014-03-24  6:49 ` [PATCH 1/6] drm/i915/vlv: Added a rendering specific Hw WA 'WaTlbInvalidateStoreDataBefore' sourab.gupta
2014-03-24  9:32   ` Chris Wilson
2014-03-24 11:20     ` Gupta, Sourab
2014-03-24 18:32       ` Ville Syrjälä
2014-03-24 18:47         ` Chris Wilson
2014-03-25  5:17           ` Gupta, Sourab
2014-03-25  8:31           ` [PATCH v5] " sourab.gupta
2014-03-25  9:15             ` Chris Wilson
2014-03-25  9:39               ` Gupta, Sourab
2014-03-25  9:53               ` [PATCH v6] " sourab.gupta
2014-03-25 10:59                 ` Chris Wilson
2014-03-26  5:14                   ` Gupta, Sourab
2014-03-26  7:54                     ` Chris Wilson
2014-03-26 14:13                       ` Gupta, Sourab
2014-03-24  6:49 ` [PATCH 2/6] drm/i915/vlv: Added a rendering specific Hw WA 'WaSendDummy3dPrimitveAfterSetContext' sourab.gupta
2014-03-24  9:31   ` Daniel Vetter
2014-03-24 11:11     ` Gupta, Sourab
2014-03-24  9:39   ` Chris Wilson
2014-03-24  6:49 ` [PATCH 3/6] drm/i915: Enabling the TLB invalidate bit in GFX Mode register sourab.gupta
2014-03-24  9:35   ` Chris Wilson
2014-03-24  6:49 ` [PATCH 4/6] drm/i915/vlv: Remove the enabling of VS_TIMER_DISPATCH bit in MI MODE reg sourab.gupta
2014-03-24  6:49 ` [PATCH 5/6] drm/i915/vlv:Implement WaDisable_RenderCache_OperationalFlush sourab.gupta
2014-03-24  9:32   ` Chris Wilson
2014-03-24  6:49 ` [PATCH 6/6] drm/i915/vlv: Modified Implementation of WaDisableL3Bank2xClockGate sourab.gupta
2014-03-24  9:41   ` Chris Wilson
2014-03-24  9:35 ` Daniel Vetter [this message]
2014-03-24 11:05   ` [PATCH 0/6] Rendering Specific HW Workarounds for VLV Gupta, Sourab
  -- strict thread matches above, loose matches on Subject: below --
2014-03-24 17:30 sourab.gupta
2014-01-22  3:45 [PATCH 0/6] Rendering specific Hw workarounds " akash.goel

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=20140324093509.GD26878@phenom.ffwll.local \
    --to=daniel@ffwll.ch \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=sourab.gupta@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox