From: Arun Siluvery <arun.siluvery@linux.intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH v2 0/8] Gen9 HW whitelist and Preemption WA patches
Date: Thu, 21 Jan 2016 16:07:22 +0000 [thread overview]
Message-ID: <56A1023A.7020904@linux.intel.com> (raw)
In-Reply-To: <20160121151723.GM16147@nuc-i3427.alporthouse.com>
On 21/01/2016 15:17, Chris Wilson wrote:
> On Thu, Jan 21, 2016 at 02:00:39PM +0000, Arun Siluvery wrote:
>> Resending all patches as told by Daniel because I didn't use correct
>> message-id while replying updated version of Patch1 before which means
>> patchwork won't pickup and we won't have CI results. Previous updates
>> regarding Patch1 are available at https://patchwork.freedesktop.org/patch/70527/
>>
>> Some of the WA patches are now reviewed so I added r-b tags for them.
>>
>> Reviewed: 1, 2, 3, 5, 6
>> Updated: 4 (to address review comment)
>> To be reviewed: 4, 7, 8
>>
>> Arun Siluvery (8):
>> drm/i915/gen9: Add framework to whitelist specific GPU registers
>> drm/i915/gen9: Add GEN8_CS_CHICKEN1 to HW whitelist
>> drm/i915/gen9: Add HDC_CHICKEN1 to HW whitelist
>> drm/i915/bxt: Add GEN9_CS_DEBUG_MODE1 to HW whitelist
>> drm/i915/bxt: Add GEN8_L3SQCREG4 to HW whitelist
>> drm/i915/skl: Add GEN8_L3SQCREG4 to HW whitelist
>> drm/i915/skl: Enable Per context Preemption granularity control
>> drm/i915/gen9: Add WaOCLCoherentLineFlush
>
> With bland changelogs, it is impossible to assess the severity of the
> issues being addressed. How many of these do we need to apply to kernel
> release to address potential user impact? Which do backporters need?
> Are they critical stability fixes or power tuning or enabling for future
> features?
> -Chris
>
All of these changes are required for Preemption so they affect Gen9
only. The whitelist changes are really to support for preemption WA that
are going to be part of UMD. The WA data is sketchy and for some of them
hsd links are not available so I don't really know the details.
regards
Arun
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-01-21 16:08 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-21 14:00 [PATCH v2 0/8] Gen9 HW whitelist and Preemption WA patches Arun Siluvery
2016-01-21 14:00 ` [PATCH v2 1/8] drm/i915/gen9: Add framework to whitelist specific GPU registers Arun Siluvery
2016-01-21 14:00 ` [PATCH v2 2/8] drm/i915/gen9: Add GEN8_CS_CHICKEN1 to HW whitelist Arun Siluvery
2016-01-21 14:00 ` [PATCH v2 3/8] drm/i915/gen9: Add HDC_CHICKEN1 " Arun Siluvery
2016-01-21 14:00 ` [PATCH v2 4/8] drm/i915/bxt: Add GEN9_CS_DEBUG_MODE1 " Arun Siluvery
2016-01-21 14:40 ` Nick Hoath
2016-01-21 14:00 ` [PATCH v2 5/8] drm/i915/bxt: Add GEN8_L3SQCREG4 " Arun Siluvery
2016-01-21 14:00 ` [PATCH v2 6/8] drm/i915/skl: " Arun Siluvery
2016-01-21 14:00 ` [PATCH v2 7/8] drm/i915/skl: Enable Per context Preemption granularity control Arun Siluvery
2016-01-21 14:41 ` Nick Hoath
2016-01-21 14:00 ` [PATCH v2 8/8] drm/i915/gen9: Add WaOCLCoherentLineFlush Arun Siluvery
2016-01-21 14:42 ` Nick Hoath
2016-01-21 14:25 ` ✗ Fi.CI.BAT: warning for Gen9 HW whitelist and Preemption WA patches (rev2) Patchwork
2016-01-21 14:36 ` Arun Siluvery
2016-01-21 15:17 ` [PATCH v2 0/8] Gen9 HW whitelist and Preemption WA patches Chris Wilson
2016-01-21 16:07 ` Arun Siluvery [this message]
2016-01-21 16:56 ` Chris Wilson
2016-01-21 17:35 ` Arun Siluvery
2016-01-25 18:01 ` Daniel Vetter
2016-01-25 18:23 ` Arun Siluvery
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=56A1023A.7020904@linux.intel.com \
--to=arun.siluvery@linux.intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=intel-gfx@lists.freedesktop.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