Re: [Intel-gfx] [CI 16/20] drm/i915: Only query timestamp when measuring elapsed time

2016-05-23 Thread Tvrtko Ursulin
On 20/05/16 13:20, Chris Wilson wrote: On Thu, May 19, 2016 at 04:44:03PM +0100, Tvrtko Ursulin wrote: On 19/05/16 12:32, Chris Wilson wrote: Avoid the two calls to ktime_get_raw_ns() (at best it reads the TSC) as we only need to compute the elapsed time for a timed wait. v2: Eliminate the u

Re: [Intel-gfx] [CI 16/20] drm/i915: Only query timestamp when measuring elapsed time

2016-05-20 Thread Chris Wilson
On Thu, May 19, 2016 at 04:44:03PM +0100, Tvrtko Ursulin wrote: > > On 19/05/16 12:32, Chris Wilson wrote: > >Avoid the two calls to ktime_get_raw_ns() (at best it reads the TSC) as > >we only need to compute the elapsed time for a timed wait. > > > >v2: Eliminate the unused local variable reducin

Re: [Intel-gfx] [CI 16/20] drm/i915: Only query timestamp when measuring elapsed time

2016-05-19 Thread Tvrtko Ursulin
On 19/05/16 12:32, Chris Wilson wrote: Avoid the two calls to ktime_get_raw_ns() (at best it reads the TSC) as we only need to compute the elapsed time for a timed wait. v2: Eliminate the unused local variable reducing the function size by 64 bytes (using the storage space on the callers stack

[Intel-gfx] [CI 16/20] drm/i915: Only query timestamp when measuring elapsed time

2016-05-19 Thread Chris Wilson
Avoid the two calls to ktime_get_raw_ns() (at best it reads the TSC) as we only need to compute the elapsed time for a timed wait. v2: Eliminate the unused local variable reducing the function size by 64 bytes (using the storage space on the callers stack rather than adding to our stack frame) Si