From mboxrd@z Thu Jan 1 00:00:00 1970 From: Arjan van de Ven Subject: Re: [Intel-gfx] [PATCH] drm/i915: add a tracepoint for gpu frequency changes Date: Sat, 01 Sep 2012 11:28:55 -0700 Message-ID: <504253E7.9050207@linux.intel.com> References: <1346326008-11186-1-git-send-email-daniel.vetter@ffwll.ch> <06ae216a0855cba921de7ebdcc75acb4@bwidawsk.net> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <06ae216a0855cba921de7ebdcc75acb4@bwidawsk.net> List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org Errors-To: dri-devel-bounces+sf-dri-devel=m.gmane.org@lists.freedesktop.org To: Ben Widawsky Cc: Daniel Vetter , Intel Graphics Development , DRI Development List-Id: dri-devel@lists.freedesktop.org On 9/1/2012 11:26 AM, Ben Widawsky wrote: > On 2012-08-30 04:26, Daniel Vetter 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 >> Signed-off-by: Daniel Vetter > > I can't help but think it's equally interesting to know when the queue the work as well. > > btw... if the userspace interface (e.g. the actual event) is not controversial and very unlikely to change, I'd like to start coding the powertop support for this already....