Re: [Intel-gfx] [PATCH 2/5] drm/i915: Split out functions for different kinds of workarounds

2018-02-13 Thread Chris Wilson
Quoting Oscar Mateo (2018-02-13 21:36:34) > > > On 2/13/2018 12:54 PM, Chris Wilson wrote: > > Quoting Oscar Mateo (2018-02-13 19:13:29) > >> There are different kind of workarounds (those that modify registers that > >> live in the context image, those that modify global registers, those that >

Re: [Intel-gfx] [PATCH 2/5] drm/i915: Split out functions for different kinds of workarounds

2018-02-13 Thread Oscar Mateo
On 2/13/2018 12:54 PM, Chris Wilson wrote: Quoting Oscar Mateo (2018-02-13 19:13:29) There are different kind of workarounds (those that modify registers that live in the context image, those that modify global registers, those that whitelist registers, etc...) and they have different requirem

Re: [Intel-gfx] [PATCH 2/5] drm/i915: Split out functions for different kinds of workarounds

2018-02-13 Thread Chris Wilson
Quoting Oscar Mateo (2018-02-13 19:13:29) > There are different kind of workarounds (those that modify registers that > live in the context image, those that modify global registers, those that > whitelist registers, etc...) and they have different requirements in terms > of where they are applied

[Intel-gfx] [PATCH 2/5] drm/i915: Split out functions for different kinds of workarounds

2018-02-13 Thread Oscar Mateo
There are different kind of workarounds (those that modify registers that live in the context image, those that modify global registers, those that whitelist registers, etc...) and they have different requirements in terms of where they are applied and how. Also, by splitting them apart, it should