From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Arjan van de Ven <arjan@linux.intel.com>
Cc: otaylor@gtk.org, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: boost GPU and CPU freq when leaving idle
Date: Fri, 28 Jun 2013 12:14:17 -0700 [thread overview]
Message-ID: <20130628121417.7e8c1b3d@jbarnes-desktop> (raw)
In-Reply-To: <51CDDFBB.2050704@linux.intel.com>
On Fri, 28 Jun 2013 12:10:51 -0700
Arjan van de Ven <arjan@linux.intel.com> wrote:
> On 6/28/2013 11:37 AM, Chris Wilson wrote:
> > On Fri, Jun 28, 2013 at 09:54:32AM -0700, Jesse Barnes wrote:
> >> Coming out of idle is usually due to some sort of user input (swiping a
> >> screen, clicking a button) and often results in some sort of graphical
> >> animation. To prevent stutter for a CPU or GPU intensive animation,
> >> boost the GPU and CPU freq to the maximum to get the first frame out as
> >> quickly as possible. The normal CPU and GPU frequency management code
> >> will take over from there and (hopefully) clock down to save power as
> >> needed if the max frequencies aren't required.
> >>
> >> This could probably be done more cleanly, and possibly without another
> >> uncached read in the execbuf path if we tracked idleness elsewhere. I'm
> >> also unsure about the cpufreq calls; I don't really know if this will do
> >> what I want...
> >
> > Would seem like a good idea to make intel_mark_busy() dtrt and use them.
> > -Chris
> >
>
> Is there a way to force the GPU always to run at the top speed?
> (since it might well be the most efficient way to run things due to race-to-halt)
Yeah I posted a patch for that earlier; adds a new i915.enable_turbo
param. If disabled, it just always runs at top speed when not in C6.
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2013-06-28 19:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-28 16:54 [PATCH] drm/i915: boost GPU and CPU freq when leaving idle Jesse Barnes
2013-06-28 18:37 ` Chris Wilson
2013-06-28 18:40 ` Jesse Barnes
2013-06-28 19:27 ` Chris Wilson
2013-06-28 19:10 ` Arjan van de Ven
2013-06-28 19:14 ` Jesse Barnes [this message]
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=20130628121417.7e8c1b3d@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=arjan@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=otaylor@gtk.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox