All of lore.kernel.org
 help / color / mirror / Atom feed
From: Arjan van de Ven <arjan@linux.intel.com>
To: Ben Widawsky <ben@bwidawsk.net>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>,
	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: Sat, 01 Sep 2012 20:06:22 -0700	[thread overview]
Message-ID: <5042CD2E.8070609@linux.intel.com> (raw)
In-Reply-To: <8b090ff7727bab7725e0a62fcf9d265e@bwidawsk.net>

On 9/1/2012 8:05 PM, Ben Widawsky wrote:
> , from a single trace event you should know the current frequency and the previous frequency.
but if you're doing a heavy game or whatever... you may stay at the highest all the time,
and I get no information...
same for getting stuck or being always low.

  reply	other threads:[~2012-09-02  3:06 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               ` Arjan van de Ven [this message]
2012-09-02  3:11                 ` [Intel-gfx] " Ben Widawsky
2012-09-03  7:56             ` Daniel Vetter
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=5042CD2E.8070609@linux.intel.com \
    --to=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.