public inbox for intel-gfx@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Ben Widawsky <benjamin.widawsky@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
	Abdiel Janulgue <abdiel.janulgue@linux.intel.com>,
	Timo Aaltonen <tjaalton@ubuntu.com>,
	stable@vger.kernel.org
Subject: Re: [PATCH 2/2] drm/i915/skl: Fix spurious gpu hang with gt3/gt4 revs
Date: Wed, 13 Apr 2016 15:43:23 +0300	[thread overview]
Message-ID: <87ega9of10.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <20160405154446.GA28348@intel.com>

Ben Widawsky <benjamin.widawsky@intel.com> writes:

> [ text/plain ]
> On Tue, Apr 05, 2016 at 03:56:17PM +0300, Mika Kuoppala wrote:
>> Experiments with heaven 4.0 benchmark and skylake gt3e (rev 0xa)
>> suggest that WaForceContextSaveRestoreNonCoherent is needed for all
>> revs. Extending this to all revs cures a gpu hang with rev 0xa when
>> running heaven4.0 gpu benchmark.
>> 
>> We have been here before, with problems enabling gt4e and extending
>> up to revision F0 instead of false claims of bspec of E0 only. See
>> commit <e238659ddd88> ("drm/i915/skl: Default to noncoherent access
>> up to F0"). In retrospect we should have covered this with this big
>> blanket back then already, as E0 vs F0 discrepancy was suspicious
>> enough.
>> 
>> Previously the WaForceEnableNonCoherent has been tied to
>> context non-coherence, atleast in relevant hsds. So keep this tie
>> and extended this alongside.
>> 
>> Cc: Abdiel Janulgue <abdiel.janulgue@linux.intel.com>
>> Cc: Ben Widawsky <benjamin.widawsky@intel.com>
>> Cc: Timo Aaltonen <tjaalton@ubuntu.com>
>> Cc: stable@vger.kernel.org
>> Reported-by: Mike Lothian <mike@fireburn.co.uk>
>> References: https://bugs.freedesktop.org/show_bug.cgi?id=93491
>> Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
>
> I don't have a reproducible hang, but both are:
> Reviewed-by: Ben Widawsky <benjamin.widawsky@intel.com>
>

Both patches pushed to dinq. Thanks for review and testing.

-MIka

> -- 
> Ben Widawsky, Intel Open Source Technology Center

  reply	other threads:[~2016-04-13 12:43 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-05 12:56 [PATCH 1/2] drm/i915/skl: Fix rc6 based gpu/system hang Mika Kuoppala
2016-04-05 12:56 ` [PATCH 2/2] drm/i915/skl: Fix spurious gpu hang with gt3/gt4 revs Mika Kuoppala
2016-04-05 14:07   ` Jani Nikula
2016-04-05 15:44   ` Ben Widawsky
2016-04-13 12:43     ` Mika Kuoppala [this message]
2016-04-05 13:02 ` [PATCH 1/2] drm/i915/skl: Fix rc6 based gpu/system hang Timo Aaltonen
2016-04-05 15:35 ` ✓ Fi.CI.BAT: success for series starting with [1/2] " Patchwork

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=87ega9of10.fsf@gaia.fi.intel.com \
    --to=mika.kuoppala@linux.intel.com \
    --cc=abdiel.janulgue@linux.intel.com \
    --cc=benjamin.widawsky@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=stable@vger.kernel.org \
    --cc=tjaalton@ubuntu.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