On Thu, Jan 21, 2016 at 02:54:03PM +0100, Lucas Stach wrote: > The retire worker is kicked for each fence, either the normal way > by signaling the fence from the event completion interrupt or by > the recover worker if the GPU got stuck. Moving the RPM put into > the retire worker allows us to have it in a single place for > both cases. > > This also shaves off quite a bit of the CPU time spent in hardirq > context, as arming the autosuspend timer when the RPM refcount > drops to 0 is a relatively costly operation. > > Signed-off-by: Lucas Stach <l.stach@xxxxxxxxxxxxxx> Tested-by: Russell King <rmk+kernel@xxxxxxxxxxxxxxxx> Acked-by: Russell King <rmk+kernel@xxxxxxxxxxxxxxxx> Thanks. -- RMK's Patch system: http://www.arm.linux.org.uk/developer/patches/ FTTC broadband for 0.8mile line: currently at 9.6Mbps down 400kbps up according to speedtest.net. _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
