Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Chris Wilson <chris@chris-wilson.co.uk>
To: Jesse Barnes <jbarnes@virtuousgeek.org>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 2/2] drm/i915: load a ring frequency scaling table
Date: Mon, 27 Jun 2011 20:40:08 +0100	[thread overview]
Message-ID: <1309203608_30586@CP5-2952> (raw)
In-Reply-To: <1308939194-3568-2-git-send-email-jbarnes@virtuousgeek.org>

On Fri, 24 Jun 2011 11:13:14 -0700, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> The ring frequency scaling table tells the PCU to treat certain GPU
> frequencies as if they were a given CPU frequency for purposes of
> scaling the ring frequency.  Normally the PCU will scale the ring
> frequency based on the CPU P-state, but with the table present, it will
> also take the GPU frequency into account.

So it wasn't picking up max-cpu-freq even though I have CONFIG_CPU_FREQ
and the various ACPI and Intel cpu drivers.

Taking a hint from x86/kvm, I used tsc_khz instead of the default 3000.

nexuiz @10x7  nopatch -> 3000 -> 3300 [tsc_khz]
uncached:     43.2       44.4    44.8
     llc:     51.3               52.3

At max_freq=3000, a cpu busy loop was still able to nudge it up to the
same speed as using the max_freq=3300 value.
-Chris

-- 
Chris Wilson, Intel Open Source Technology Centre

  parent reply	other threads:[~2011-06-27 19:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-06-24 18:13 [PATCH 1/2] cpufreq: expose a cpufreq_quick_get_max routine Jesse Barnes
2011-06-24 18:13 ` [PATCH 2/2] drm/i915: load a ring frequency scaling table Jesse Barnes
2011-06-27 17:54   ` Eric Anholt
2011-06-28 17:40     ` Jesse Barnes
2011-06-27 19:40   ` Chris Wilson [this message]
2011-06-28 17:41     ` Jesse Barnes
2011-06-27 19:03 ` [PATCH 1/2] cpufreq: expose a cpufreq_quick_get_max routine 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=1309203608_30586@CP5-2952 \
    --to=chris@chris-wilson.co.uk \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=jbarnes@virtuousgeek.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