Re: [PATCH v3 00/22] Refactor HW workaround code

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

 





On 10/17/2017 06:06 AM, Chris Wilson wrote:
Quoting Oscar Mateo (2017-10-13 21:53:54)
Main difference with v2 is the split into GT and Display workarounds (suggested
by Ville). Because that makes review even more important (which WA goes where?)
I have split the movement of WAs from init_clock_gating into separate patches
(one per GEN).

Currently, deciding how/where to apply new workarounds is challenging. Often,
workarounds end up applied incorrectly and get lost under certain circumstances
(e.g. a context switch or a GPU reset). This is a proposal to attempt to
eliminate some of this pain, by clarifying the current classification of
workarounds (context saved/restored, global registers, whitelisting, BB),
putting them together on the same file, and improving the existing validation
infrastructure (debugfs/i-g-t).
Some more to add to the list! i915_gem_init_hw() has another random
collection of GT registers.
-Chris

Hmmmm... those are very old (IVB, HSW...) and I had started converting only BDW onwards (if only because, the older the platform gets, the more difficult it is to classify WAs).
_______________________________________________
Intel-gfx mailing list
Intel-gfx@xxxxxxxxxxxxxxxxxxxxx
https://lists.freedesktop.org/mailman/listinfo/intel-gfx




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