From: Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
To: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>,
Intel-gfx@lists.freedesktop.org
Cc: Anuj Phogat <anuj.phogat@intel.com>,
kevin.ma@intel.com, xiaogang.li@intel.com
Subject: Re: [PATCH v2] drm/i915/icl: Whitelist GEN9_SLICE_COMMON_ECO_CHICKEN1
Date: Tue, 30 Apr 2019 07:57:41 +0100 [thread overview]
Message-ID: <592d13b5-3c9c-9d72-dbb5-ad678ef53f3d@linux.intel.com> (raw)
In-Reply-To: <155660718209.4262.16653554075363334160@jlahtine-desk.ger.corp.intel.com>
On 30/04/2019 07:53, Joonas Lahtinen wrote:
> Quoting Tvrtko Ursulin (2019-04-18 13:06:34)
>> From: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
>>
>> WaEnableStateCacheRedirectToCS context workaround configures the L3 cache
>> to benefit 3d workloads but media has different requirements.
>>
>> Remove the workaround and whitelist the register to allow any userspace
>> configure the behaviour to their liking.
>>
>> v2:
>> * Remove the workaround apart from adding the whitelist.
>
> Please add the information that removal of the workaround doesn't cause
> any ill effects with old Mesa and add Fixes:, so this gets picked up to
> 5.2. No need for stable as Icelake is alpha_support before 5.2
>
> With those changes this is:
>
> Reviewed-by: Joonas Lahtinen <joonas.lahtinen@linux.intel.com>
Pushed. Thanks for all the testing on both sides!
Regards,
Tvrtko
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2019-04-30 6:57 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-15 11:43 [PATCH] drm/i915/icl: Whitelist GEN9_SLICE_COMMON_ECO_CHICKEN1 Tvrtko Ursulin
2019-04-15 11:45 ` Chris Wilson
2019-04-15 12:25 ` Tvrtko Ursulin
2019-04-15 16:17 ` Chris Wilson
2019-04-15 12:38 ` ✓ Fi.CI.BAT: success for " Patchwork
2019-04-15 14:24 ` ✓ Fi.CI.IGT: " Patchwork
2019-04-18 10:06 ` [PATCH v2] " Tvrtko Ursulin
2019-04-26 8:13 ` Lionel Landwerlin
2019-04-26 8:31 ` Joonas Lahtinen
2019-04-26 16:58 ` Anuj Phogat
2019-04-29 5:57 ` Tvrtko Ursulin
2019-04-29 17:16 ` Anuj Phogat
2019-04-30 1:25 ` Li, Xiaogang
2019-04-26 17:01 ` Anuj Phogat
2019-04-30 6:53 ` Joonas Lahtinen
2019-04-30 6:57 ` Tvrtko Ursulin [this message]
2019-04-18 11:28 ` ✓ Fi.CI.BAT: success for drm/i915/icl: Whitelist GEN9_SLICE_COMMON_ECO_CHICKEN1 (rev2) Patchwork
2019-04-18 13:12 ` ✓ 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=592d13b5-3c9c-9d72-dbb5-ad678ef53f3d@linux.intel.com \
--to=tvrtko.ursulin@linux.intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=anuj.phogat@intel.com \
--cc=joonas.lahtinen@linux.intel.com \
--cc=kevin.ma@intel.com \
--cc=xiaogang.li@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