From mboxrd@z Thu Jan  1 00:00:00 1970
From: Jesse Barnes <jbarnes@virtuousgeek.org>
Subject: Re: [PATCH 2/2] drm/i915: load a ring frequency scaling
 table
Date: Tue, 28 Jun 2011 10:41:51 -0700
Message-ID: <20110628104151.62447f31@jbarnes-desktop>
References: <1308939194-3568-1-git-send-email-jbarnes@virtuousgeek.org>
	<1308939194-3568-2-git-send-email-jbarnes@virtuousgeek.org>
	<1309203608_30586@CP5-2952>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org>
Received: from oproxy7-pub.bluehost.com (oproxy7-pub.bluehost.com
	[67.222.55.9])
	by gabe.freedesktop.org (Postfix) with SMTP id 4A1C09E880
	for <intel-gfx@lists.freedesktop.org>;
	Tue, 28 Jun 2011 10:42:01 -0700 (PDT)
In-Reply-To: <1309203608_30586@CP5-2952>
List-Unsubscribe: <http://lists.freedesktop.org/mailman/options/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=unsubscribe>
List-Archive: <http://lists.freedesktop.org/archives/intel-gfx>
List-Post: <mailto:intel-gfx@lists.freedesktop.org>
List-Help: <mailto:intel-gfx-request@lists.freedesktop.org?subject=help>
List-Subscribe: <http://lists.freedesktop.org/mailman/listinfo/intel-gfx>,
	<mailto:intel-gfx-request@lists.freedesktop.org?subject=subscribe>
Sender: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
Errors-To: intel-gfx-bounces+gcfxdi-intel-gfx=m.gmane.org@lists.freedesktop.org
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: intel-gfx@lists.freedesktop.org
List-Id: intel-gfx@lists.freedesktop.org

On Mon, 27 Jun 2011 20:40:08 +0100
Chris Wilson <chris@chris-wilson.co.uk> wrote:

> 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.

Ok tsc_khz is a good fallback, thanks.

-- 
Jesse Barnes, Intel Open Source Technology Center