From: Daniel Vetter <daniel@ffwll.ch>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
Ben Widawsky <ben@bwidawsk.net>,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>,
DRI Development <dri-devel@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: add a tracepoint for gpu frequency changes
Date: Mon, 3 Sep 2012 09:56:33 +0200 [thread overview]
Message-ID: <20120903075633.GG5225@phenom.ffwll.local> (raw)
In-Reply-To: <5042C801.9080200@linux.intel.com>
On Sat, Sep 01, 2012 at 07:44:17PM -0700, Arjan van de Ven wrote:
> On 9/1/2012 6:36 PM, Ben Widawsky wrote:
>
> > It depends on what you're trying to measure. I think this patch is quite useful but I think I'll make you defend your patch now since you're the maintainer and you took
> > your own patch and you're shooting down my idea. So please tell me what PowerTOP should do with this patch other than notice we're stuck (and furthermore, even if we're
> > stuck, what should it tell us to do)?
>
> what I would like to do, as the powertop guy.... is to show frequency stats similar to how we do that
> for CPUs. E.g. as close as to actual as we can get.
> few questions:
> 1) Can I read the momentary frequency somewhere?
> (it's great to get change events, but I also need a start frequency, otherwise I have a gap in
> knowledge from start of measurement to first change event)
Oops, forgotten about this, but it looks like Ben has already volunteered
himself for those ;-)
> 2) Can I read a "hardware average" somewhere, similar to what we can do for cpus ?
Afaik, there's nothing. But since the cpu controls the gpu freq
completely, you can just compute those yourselves from the tracepoints.
Together with the rc6 residency timers we already expose this should give
a neat overview of how busy the gpu is and how much power it blows through
-Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-09-03 7:56 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-30 11:26 [PATCH] drm/i915: add a tracepoint for gpu frequency changes Daniel Vetter
2012-08-30 13:34 ` [Intel-gfx] " Chris Wilson
2012-08-31 9:07 ` Daniel Vetter
2012-08-30 13:51 ` Paul Menzel
2012-09-01 18:26 ` [Intel-gfx] " Ben Widawsky
2012-09-01 18:28 ` Arjan van de Ven
2012-09-01 18:35 ` Ben Widawsky
2012-09-01 19:14 ` Daniel Vetter
2012-09-02 1:36 ` Ben Widawsky
2012-09-02 2:44 ` Arjan van de Ven
2012-09-02 3:05 ` Ben Widawsky
2012-09-02 3:06 ` [Intel-gfx] " Arjan van de Ven
2012-09-02 3:11 ` Ben Widawsky
2012-09-03 7:56 ` Daniel Vetter [this message]
2012-09-03 7:53 ` Daniel Vetter
2012-09-01 19:22 ` [Intel-gfx] " Chris Wilson
2012-09-02 1:16 ` Ben Widawsky
2012-09-02 7:41 ` Chris Wilson
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20120903075633.GG5225@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=arjan@linux.intel.com \
--cc=ben@bwidawsk.net \
--cc=daniel.vetter@ffwll.ch \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.