[PATCH] drm/i915: WA: FBC Render Nuke.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



please just ignore this version...
going to try fbc_dirty and other changes here...

On Thu, Jun 6, 2013 at 12:00 PM, Chris Wilson <chris at chris-wilson.co.uk> wrote:
> On Thu, Jun 06, 2013 at 11:49:56AM -0300, Rodrigo Vivi wrote:
>> WaFbcNukeOn3DBlt for IVB, HSW.
>>
>> According BSPec: "Workaround: Do not enable Render Command Streamer tracking for FBC.
>> Instead insert a LRI to address 0x50380 with data 0x00000004 after the PIPE_CONTROL that
>> follows each render submission."
>>
>> v2: Chris noticed that flush_domains check was missing here and also suggested to do
>>     LRI only when fbc is enabled. To avoid do a I915_READ on every flush lets use the
>>     module parameter check.
>>
>> v3: Adding Wa name as Damien suggested.
>>
>> v4: Ville noticed VLV doesn't support fbc at all and comment came wrong from spec.
>>
>> v5: Ville noticed than on blt a Cache Clean LRI should be used instead the Nuke one.
>>
>> v6: Check for flush domain on blt (by Ville).
>>     Check for scanout dirty (by Chris).
> Note quite what I had in mind, see
> https://patchwork.kernel.org/patch/2606131/
> -Chris
>
> --
> Chris Wilson, Intel Open Source Technology Centre



-- 
Rodrigo Vivi
Blog: http://blog.vivi.eng.br


[Index of Archives]     [Linux USB Devel]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux