From: Jesse Barnes <jbarnes@virtuousgeek.org>
To: Joe Bloggsian <joebloggsian@gmail.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: IVB GPU turbo
Date: Tue, 22 May 2012 09:23:52 -0700 [thread overview]
Message-ID: <20120522092352.4457a804@jbarnes-desktop> (raw)
In-Reply-To: <CACNTD9u52ZNLk8HY+St4cBQAT7ZQkC9q5AqvgA5PTfH1UDKHuQ@mail.gmail.com>
On Tue, 22 May 2012 17:14:11 +0100
Joe Bloggsian <joebloggsian@gmail.com> wrote:
> Thanks for the help, I've had time to build and test a few kernels on
> various systems following your advice.
>
> In summary I need both a new drm-intel-next kernel from Daniel's tree *and*
> the patch you suggest to get expected GPU turbo behaviour, compared to a
> stable 3.2 kernel.
>
> Test results from Core i7 3770 / HD4000: With just the latest drm-intel-next
> kernel (commit 98b6bd), the symptoms are as before, max GPU turbo of 600MHz
> in the test app. With just the (equivalent of the) patch applied to a
> 3.2.18 kernel, the max turbo is better (>600) but still often less than
> expected. With both patch and kernel, the GPU immediately spins up to
> 1.15GHz and stays there, as expected - and the measured test app
> performance is nearly twice what I get with the up to date Ubuntu 12.04 x64
> kernel!
Awesome, thanks so much for testing, I'll send the patch upstream now.
> I've also seen the full turbo kick in for other media workloads with the
> default kernel, but one way of reliably reproducing this problem for me is
> to run the avcenc test app that is part of libva.
>
> The same problem exists on Sandy Bridge. Although the turbo and performance
> gaps between the latest released Ubuntu 12.04 kernel and the patched 3.4
> kernel are less than Ivy Bridge, they are still significant on my core i3
> 2310M / HD3000 laptop.
Ok good to know; the patch will apply to SNB too, the fact you tested
things there makes my life easier. :)
--
Jesse Barnes, Intel Open Source Technology Center
prev parent reply other threads:[~2012-05-22 16:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-17 20:11 IVB GPU turbo Joe Bloggsian
2012-05-18 21:25 ` Jesse Barnes
2012-05-22 16:14 ` Joe Bloggsian
2012-05-22 16:23 ` 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=20120522092352.4457a804@jbarnes-desktop \
--to=jbarnes@virtuousgeek.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=joebloggsian@gmail.com \
/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