From: Mika Kuoppala <mika.kuoppala@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
Intel-gfx@lists.freedesktop.org,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Revert "drm/i915/tgl: Wa_1607138340"
Date: Thu, 09 Jan 2020 10:46:02 +0200 [thread overview]
Message-ID: <87pnftf25x.fsf@gaia.fi.intel.com> (raw)
In-Reply-To: <157850084100.13423.10479098209136206233@skylake-alporthouse-com>
Chris Wilson <chris@chris-wilson.co.uk> writes:
> Quoting Tvrtko Ursulin (2020-01-08 16:19:54)
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> This reverts commit 08fff7aeddc9dd72161b4c8fc27fbab12b4b9352.
>>
>> For some yet unexplained reason not having this improves stability of some
>> media workloads.
>>
>> Promise is that the media hang will be root caused properly and in the
>> meantime absence of this workaround is unlikely to cause problems.
>
> I suspect this is shooting the messenger. The danger is that we rely on
> FORCE_RESTORE for preemption, and so if this bit is triggering the issue,
> their problem just becomes more sporadic.
Noted. But lets get a sample point with A0. We kind
of know where to focus our gaze from now on.
Acked-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-01-09 8:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-08 16:19 [Intel-gfx] [PATCH] drm/i915: Revert "drm/i915/tgl: Wa_1607138340" Tvrtko Ursulin
2020-01-08 16:27 ` Chris Wilson
2020-01-09 8:46 ` Mika Kuoppala [this message]
2020-01-09 11:25 ` [Intel-gfx] ✓ Fi.CI.BAT: success for " Patchwork
2020-01-09 21:50 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=87pnftf25x.fsf@gaia.fi.intel.com \
--to=mika.kuoppala@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=chris@chris-wilson.co.uk \
--cc=tvrtko.ursulin@linux.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 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.