On Thu, 30 Aug 2012 13:26:48 +0200, Daniel Vetter <daniel.vetter at ffwll.ch> wrote: > We've had and still have too many issues where the gpu turbot doesn't > quite to what it's supposed to do (or what we want it to do). > > Adding a tracepoint to track when the desired gpu frequence changes > should help a lot in characterizing and understanding problematic > workloads. > > Also, this should be fairly interesting for power tuning (and > especially noticing when the gpu is stuck in high frequencies, as has > happened in the past) and hence for integration into powertop and > similar tools. > > Cc: Arjan van de Ven <arjan at linux.intel.com> > Signed-off-by: Daniel Vetter <daniel.vetter at ffwll.ch>
Like it, even the naming scheme. Reviewed-by: Chris Wilson <chris at chris-wilson.co.uk> -Chris -- Chris Wilson, Intel Open Source Technology Centre