Re: [Intel-gfx] [PATCH 3/8] drm/i915: Automatic i915_switch_context for legacy

2017-11-17 Thread Mika Kuoppala
Chris Wilson writes: > Quoting Mika Kuoppala (2017-11-16 14:00:13) >> Chris Wilson writes: >> >> > During request construction, after pinning the context we know whether >> > or not we have to emit a context switch. So move this common operation >> > from every caller into i915_gem_request_allo

Re: [Intel-gfx] [PATCH 3/8] drm/i915: Automatic i915_switch_context for legacy

2017-11-16 Thread Chris Wilson
Quoting Mika Kuoppala (2017-11-16 14:00:13) > Chris Wilson writes: > > > During request construction, after pinning the context we know whether > > or not we have to emit a context switch. So move this common operation > > from every caller into i915_gem_request_alloc() itself. > > > > v2: Always

Re: [Intel-gfx] [PATCH 3/8] drm/i915: Automatic i915_switch_context for legacy

2017-11-16 Thread Mika Kuoppala
Chris Wilson writes: > During request construction, after pinning the context we know whether > or not we have to emit a context switch. So move this common operation > from every caller into i915_gem_request_alloc() itself. > > v2: Always submit the request if we emitted some commands during req

[Intel-gfx] [PATCH 3/8] drm/i915: Automatic i915_switch_context for legacy

2017-11-14 Thread Chris Wilson
During request construction, after pinning the context we know whether or not we have to emit a context switch. So move this common operation from every caller into i915_gem_request_alloc() itself. v2: Always submit the request if we emitted some commands during request construction, as typically