Re: [Intel-gfx] [RFC PATCH 01/11] drm/i915: No need for RING_MAX_NONPRIV_SLOTS space

2017-10-10 Thread Mika Kuoppala
Oscar Mateo writes: > Now that we write RING_FORCE_TO_NONPRIV registers directly to hardware, > there is no need to save space for them in the list of context workarounds. > > Signed-off-by: Oscar Mateo > Cc: Chris Wilson > Cc: Mika Kuoppala Reviewed-by: Mika Kuoppala > --- > drivers/gpu/d

Re: [Intel-gfx] [RFC PATCH 01/11] drm/i915: No need for RING_MAX_NONPRIV_SLOTS space

2017-10-09 Thread Michel Thierry
On 10/9/2017 1:58 PM, Oscar Mateo wrote: Now that we write RING_FORCE_TO_NONPRIV registers directly to hardware, there is no need to save space for them in the list of context workarounds. > Signed-off-by: Oscar Mateo Cc: Chris Wilson Cc: Mika Kuoppala Is it worth mention the commit that cha

[Intel-gfx] [RFC PATCH 01/11] drm/i915: No need for RING_MAX_NONPRIV_SLOTS space

2017-10-09 Thread Oscar Mateo
Now that we write RING_FORCE_TO_NONPRIV registers directly to hardware, there is no need to save space for them in the list of context workarounds. Signed-off-by: Oscar Mateo Cc: Chris Wilson Cc: Mika Kuoppala --- drivers/gpu/drm/i915/i915_drv.h | 8 +--- 1 file changed, 1 insertion(+), 7