From: Chris Wilson <chris@chris-wilson.co.uk>
To: Jesse Barnes <jbarnes@virtuousgeek.org>, intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 1/2] cpufreq: expose a cpufreq_quick_get_max routine
Date: Mon, 27 Jun 2011 20:03:18 +0100 [thread overview]
Message-ID: <1309201396_30454@CP5-2952> (raw)
In-Reply-To: <1308939194-3568-1-git-send-email-jbarnes@virtuousgeek.org>
On Fri, 24 Jun 2011 11:13:13 -0700, Jesse Barnes <jbarnes@virtuousgeek.org> wrote:
> This allows drivers and other code to get the max reported CPU frequency.
> Initial use is for scaling ring frequency with GPU frequency in the i915
> driver.
Note that there is a potential user of interface in
arch/x86/kvm/x86.c::kvm_timer_init().
-Chris
--
Chris Wilson, Intel Open Source Technology Centre
next prev parent reply other threads:[~2011-06-27 19:03 UTC|newest]
Thread overview: 8+ 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
2011-06-28 17:41 ` Jesse Barnes
2011-06-27 19:03 ` Chris Wilson [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-28 17:59 [PATCH 1/2] cpufreq: expose a cpufreq_quick_get_max routine Jesse Barnes
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=1309201396_30454@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