public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Oscar Mateo <oscar.mateo@intel.com>
To: "Michał Winiarski" <michal.winiarski@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	Mika Kuoppala <mika.kuoppala@intel.com>,
	Rodrigo Vivi <rodrigo.vivi@intel.com>
Subject: Re: [PATCH 1/6] drm/i915: Transform WaInPlaceDecompressionHang into a simple reg write
Date: Thu, 7 Sep 2017 08:44:52 -0700	[thread overview]
Message-ID: <441bc502-e822-edb4-feee-f954c78fa9a9@intel.com> (raw)
In-Reply-To: <20170907110314.ztgck6re45fcrc3i@mwiniars-main.ger.corp.intel.com>



On 09/07/2017 04:03 AM, Michał Winiarski wrote:
> On Wed, Sep 06, 2017 at 05:15:49PM -0700, Oscar Mateo wrote:
>> Afaict, GEN9_GAMT_ECO_REG_RW_IA does not live in the context, so writing
>> it on every context creation is overkill (and wrong).
>>
>> v2: Missing end parenthesis
> Though there was a discussion whether this belongs in init_workarounds, or
> init_clock_gating - I do believe that moving things around and/or renaming
> things is something that should be done in a separate patch.
>
> I compared modified registers with the spec. It all checks out.
> With the missing end parenthesis added (you're still missing some in a different
> patch ;) ), the whole series is:
>
> Reviewed-by: Michał Winiarski <michal.winiarski@intel.com>
>
> -Michał

Yes, I reached the same conclusion myself after seeing how many 
wrongly-applied WAs we had. I would still like to reach an agreement on 
the refactoring of the WA code, though, because the whole thing is very 
confusing as it stands now.

Thanks for the review!

-- Oscar

>> Cc: Chris Wilson <chris@chris-wilson.co.uk>
>> Cc: Mika Kuoppala <mika.kuoppala@intel.com>
>> Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
>> Signed-off-by: Oscar Mateo <oscar.mateo@intel.com>
>> ---
>>   drivers/gpu/drm/i915/intel_engine_cs.c | 25 +++++++++++++++----------
>>   1 file changed, 15 insertions(+), 10 deletions(-)

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

  reply	other threads:[~2017-09-07 15:44 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-07  0:15 [PATCH 1/6] drm/i915: Transform WaInPlaceDecompressionHang into a simple reg write Oscar Mateo
2017-09-07  0:15 ` [PATCH 2/6] drm/i915: Transform WaDisableI2mCycleOnWRPort " Oscar Mateo
2017-09-07  0:15 ` [PATCH 3/6] drm/i915: WaPushConstantDereferenceHoldDisable needs to modify a masked register Oscar Mateo
2017-09-07  0:15 ` [PATCH 4/6] drm/i915: Transform WaDisableGafsUnitClkGating into a simple reg write Oscar Mateo
2017-09-07  0:15 ` [PATCH 5/6] drm/i915: Transform WaDisableDynamicCreditSharing into a simple register write Oscar Mateo
2017-09-07  0:15 ` [PATCH 6/6] drm/i915: Transform WaDisablePooledEuLoadBalancingFix " Oscar Mateo
2017-09-07  0:38 ` ✗ Fi.CI.BAT: failure for series starting with [1/6] drm/i915: Transform WaInPlaceDecompressionHang into a simple reg write Patchwork
2017-09-07 11:03 ` [PATCH 1/6] " Michał Winiarski
2017-09-07 15:44   ` Oscar Mateo [this message]
  -- strict thread matches above, loose matches on Subject: below --
2017-09-07 15:40 Oscar Mateo

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=441bc502-e822-edb4-feee-f954c78fa9a9@intel.com \
    --to=oscar.mateo@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=michal.winiarski@intel.com \
    --cc=mika.kuoppala@intel.com \
    --cc=rodrigo.vivi@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