From: Daniel Vetter <daniel@ffwll.ch>
To: Rodrigo Vivi <rodrigo.vivi@gmail.com>
Cc: Marc Herbert <marc.herbert@intel.com>,
intel-gfx <intel-gfx@lists.freedesktop.org>
Subject: Re: [PATCH] drm/i915/skl: revert duplicated WaBarrierPerformanceFixDisable:skl
Date: Wed, 5 Aug 2015 10:17:37 +0200 [thread overview]
Message-ID: <20150805081737.GD17734@phenom.ffwll.local> (raw)
In-Reply-To: <CABVU7+tj4rkHmdHwooTD0+HHg6J8zaNmA0RKFX5eFzXiRHr2Xg@mail.gmail.com>
On Thu, Jul 30, 2015 at 02:52:07PM -0700, Rodrigo Vivi wrote:
> good catch.
>
> Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Queued for -next, thanks for the patch.
-Daniel
>
> On Wed, Jul 29, 2015 at 12:21 PM, Marc Herbert <marc.herbert@intel.com> wrote:
> > With this simple git diff command one can see that skl_init_workarounds()
> > got two copies of WaBarrierPerformanceFixDisable:skl:
> >
> > git diff -U21 ca6e4405779e^1 ca6e4405779e drivers/gpu/drm/i915/intel_ringbuffer.c
> >
> > This happened when the backmerge of drm-intel-fixes-2015-07-15
> > Merged the same fix on both sides. Same fix but not identical enough for
> > git: with a different surrounding context; hence the code duplication.
> >
> > This commit merely reverts the output of the git command above
> > = the duplication introduced in the backmerge.
> >
> > (This duplication was found while running git sanity checks on a
> > _linearized_ i915 forklift for ChromeOS.)
> >
> > Signed-off-by: Marc Herbert <marc.herbert@intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_ringbuffer.c | 7 -------
> > 1 file changed, 7 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_ringbuffer.c b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > index 177f7ed16cf0..1c14233d179f 100644
> > --- a/drivers/gpu/drm/i915/intel_ringbuffer.c
> > +++ b/drivers/gpu/drm/i915/intel_ringbuffer.c
> > @@ -1041,13 +1041,6 @@ static int skl_init_workarounds(struct intel_engine_cs *ring)
> > WA_SET_BIT_MASKED(HIZ_CHICKEN,
> > BDW_HIZ_POWER_COMPILER_CLOCK_GATING_DISABLE);
> >
> > - if (INTEL_REVID(dev) == SKL_REVID_C0 ||
> > - INTEL_REVID(dev) == SKL_REVID_D0)
> > - /* WaBarrierPerformanceFixDisable:skl */
> > - WA_SET_BIT_MASKED(HDC_CHICKEN0,
> > - HDC_FENCE_DEST_SLM_DISABLE |
> > - HDC_BARRIER_PERFORMANCE_DISABLE);
> > -
> > if (INTEL_REVID(dev) <= SKL_REVID_D0) {
> > /*
> > *Use Force Non-Coherent whenever executing a 3D context. This
> > --
> > 2.1.0
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
>
>
> --
> Rodrigo Vivi
> Blog: http://blog.vivi.eng.br
> _______________________________________________
> Intel-gfx mailing list
> Intel-gfx@lists.freedesktop.org
> http://lists.freedesktop.org/mailman/listinfo/intel-gfx
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-08-05 8:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-29 19:21 [PATCH] drm/i915/skl: revert duplicated WaBarrierPerformanceFixDisable:skl Marc Herbert
2015-07-30 21:52 ` Rodrigo Vivi
2015-08-05 8:17 ` Daniel Vetter [this message]
2015-07-30 23:32 ` shuang.he
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=20150805081737.GD17734@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=intel-gfx@lists.freedesktop.org \
--cc=marc.herbert@intel.com \
--cc=rodrigo.vivi@gmail.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