From: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
To: Mika Kuoppala <mika.kuoppala@linux.intel.com>,
intel-gfx@lists.freedesktop.org
Cc: stable@vger.kernel.org
Subject: Re: [Intel-gfx] [PATCH v7 3/3] drm/i915/icl: whitelist PS_(DEPTH|INVOCATION)_COUNT
Date: Tue, 2 Jul 2019 15:32:44 +0300 [thread overview]
Message-ID: <d1292ee6-ab77-5a3c-1a61-af74c2aaee6b@intel.com> (raw)
In-Reply-To: <87woh039g5.fsf@gaia.fi.intel.com>
On 02/07/2019 15:30, Mika Kuoppala wrote:
> Lionel Landwerlin <lionel.g.landwerlin@intel.com> writes:
>
>> The same tests failing on CFL+ platforms are also failing on ICL.
>> Documentation doesn't list the
>> WaAllowPMDepthAndInvocationCountAccessFromUMD workaround for ICL but
>> applying it fixes the same tests as CFL.
> Didn't find more documentation either but I have asked
> for the wa author for update.
I've filed an issue on the register definition (maybe a week ago), so
far no response.
Hopefully you get luckier ;)
-Lionel
>
>> v2: Use only one whitelist entry (Lionel)
>>
>> Signed-off-by: Lionel Landwerlin <lionel.g.landwerlin@intel.com>
>> Tested-by: Anuj Phogat <anuj.phogat@gmail.com>
>> Cc: stable@vger.kernel.org
> The register offsets are the same so we can't really do
> harm with this so we go with the evidence,
>
> Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com>
>
>> ---
>> drivers/gpu/drm/i915/gt/intel_workarounds.c | 13 +++++++++++++
>> 1 file changed, 13 insertions(+)
>>
>> diff --git a/drivers/gpu/drm/i915/gt/intel_workarounds.c b/drivers/gpu/drm/i915/gt/intel_workarounds.c
>> index b117583e38bb..a908d829d6bd 100644
>> --- a/drivers/gpu/drm/i915/gt/intel_workarounds.c
>> +++ b/drivers/gpu/drm/i915/gt/intel_workarounds.c
>> @@ -1138,6 +1138,19 @@ static void icl_whitelist_build(struct intel_engine_cs *engine)
>>
>> /* WaEnableStateCacheRedirectToCS:icl */
>> whitelist_reg(w, GEN9_SLICE_COMMON_ECO_CHICKEN1);
>> +
>> + /*
>> + * WaAllowPMDepthAndInvocationCountAccessFromUMD:icl
>> + *
>> + * This covers 4 register which are next to one another :
>> + * - PS_INVOCATION_COUNT
>> + * - PS_INVOCATION_COUNT_UDW
>> + * - PS_DEPTH_COUNT
>> + * - PS_DEPTH_COUNT_UDW
>> + */
>> + whitelist_reg_ext(w, PS_INVOCATION_COUNT,
>> + RING_FORCE_TO_NONPRIV_RD |
>> + RING_FORCE_TO_NONPRIV_RANGE_4);
>> break;
>>
>> case VIDEO_DECODE_CLASS:
>> --
>> 2.21.0.392.gf8f6787159e
>>
>> _______________________________________________
>> Intel-gfx mailing list
>> Intel-gfx@lists.freedesktop.org
>> https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-07-02 12:32 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-28 12:07 [PATCH v7 0/3] drm/i915: CTS fixes Lionel Landwerlin
2019-06-28 12:07 ` [PATCH v7 1/3] drm/i915: fix whitelist selftests with readonly registers Lionel Landwerlin
2019-06-28 16:28 ` Anuj Phogat
2019-06-29 13:13 ` [PATCH] " Chris Wilson
2019-06-29 14:34 ` Lionel Landwerlin
2019-07-02 11:14 ` Chris Wilson
2019-06-28 12:07 ` [PATCH v7 2/3] drm/i915: whitelist PS_(DEPTH|INVOCATION)_COUNT Lionel Landwerlin
2019-07-02 11:13 ` [Intel-gfx] " Chris Wilson
2019-07-02 12:16 ` Mika Kuoppala
2019-06-28 12:07 ` [PATCH v7 3/3] drm/i915/icl: " Lionel Landwerlin
2019-07-02 11:14 ` [Intel-gfx] " Chris Wilson
2019-07-02 12:30 ` Mika Kuoppala
2019-07-02 12:32 ` Lionel Landwerlin [this message]
2019-06-28 12:12 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: CTS fixes (rev7) Patchwork
2019-06-28 17:56 ` ✓ Fi.CI.BAT: success " Patchwork
2019-06-29 3:33 ` ✓ Fi.CI.IGT: " Patchwork
2019-06-29 13:00 ` Lionel Landwerlin
2019-07-02 11:19 ` Chris Wilson
2019-06-29 13:22 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: CTS fixes (rev8) Patchwork
2019-06-29 14:10 ` ✓ Fi.CI.BAT: success " Patchwork
2019-06-29 19:40 ` ✓ Fi.CI.IGT: " 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=d1292ee6-ab77-5a3c-1a61-af74c2aaee6b@intel.com \
--to=lionel.g.landwerlin@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=mika.kuoppala@linux.intel.com \
--cc=stable@vger.kernel.org \
/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