Re: [Intel-gfx] [PATCH] drm/i915: No busy-loop wait_for in the ring init code

2014-08-08 Thread Daniel Vetter
On Thu, Aug 07, 2014 at 03:15:32PM +0100, Chris Wilson wrote: > On Thu, Aug 07, 2014 at 04:07:59PM +0200, Daniel Vetter wrote: > > Doing a 1s wait (tops) with the cpu is a bit excessive. Tune it down > > like everything else in that code. > > > > Cc: Naresh Kumar Kachhi > > Cc: Chris Wilson > >

Re: [Intel-gfx] [PATCH] drm/i915: No busy-loop wait_for in the ring init code

2014-08-07 Thread Chris Wilson
On Thu, Aug 07, 2014 at 04:07:59PM +0200, Daniel Vetter wrote: > Doing a 1s wait (tops) with the cpu is a bit excessive. Tune it down > like everything else in that code. > > Cc: Naresh Kumar Kachhi > Cc: Chris Wilson > Signed-off-by: Daniel Vetter > --- > drivers/gpu/drm/i915/intel_ringbuffer

Re: [Intel-gfx] [PATCH] drm/i915: No busy-loop wait_for in the ring init code

2014-08-07 Thread Chris Wilson
On Thu, Aug 07, 2014 at 04:07:59PM +0200, Daniel Vetter wrote: > Doing a 1s wait (tops) with the cpu is a bit excessive. Tune it down > like everything else in that code. 1s? Didn't wait_for_atomic() take a timeout in microseconds? -Chris -- Chris Wilson, Intel Open Source Technology Centre

[Intel-gfx] [PATCH] drm/i915: No busy-loop wait_for in the ring init code

2014-08-07 Thread Daniel Vetter
Doing a 1s wait (tops) with the cpu is a bit excessive. Tune it down like everything else in that code. Cc: Naresh Kumar Kachhi Cc: Chris Wilson Signed-off-by: Daniel Vetter --- drivers/gpu/drm/i915/intel_ringbuffer.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/drivers/