From: Daniel Vetter <daniel@ffwll.ch>
To: Jerome Glisse <j.glisse@gmail.com>
Cc: cand@gmx.com, dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] radeon: Make PM info available to all, not just debug users
Date: Mon, 4 Jun 2012 21:54:33 +0200 [thread overview]
Message-ID: <20120604195433.GC29760@phenom.ffwll.local> (raw)
In-Reply-To: <CAH3drwagwUcH6saLADW-Gk2tNztpn_rZERY1nggvjM-xZf1RSQ@mail.gmail.com>
On Mon, Jun 04, 2012 at 02:18:00PM -0400, Jerome Glisse wrote:
> On Mon, Jun 4, 2012 at 1:54 PM, Martin Peres <martin.peres@free.fr> wrote:
> > Answers inlined.
> >
> > Le 04/06/2012 19:19, Jerome Glisse a écrit :
> >
> >>
> >> My point is that there is no way for power management to find an API
> >> that fits all GPU. If i were to do it now, i would have one ioctl
> >> version for r3xx, one for r5xx, one for r6xx/r7xx, one for r8xx, one
> >> for r9xx, ... yes there would be some common fields accross them.
> >
> > Right, but would the userspace care for so much information?
>
> I think it might, think about newer GPU where we could let user do a
> custom profile to restrict the GPU into some range of power
> consumption/temperature/fan speed .... What kind of information i
> would want to expose would be highly GPU family related.
In i915-land we're trying to make things Just Work. If needed we can
expose (generation/platform-specific) tunables in sysfs. But on snb and
later the combination of rc6+gpu turbo (mostly handled all by hw) is
rather ok, so I don't see anything going above and beyond a min/max
frequency limiter: Moving the min upwards would help for benchmarking,
pushing the max doin might help conserver power for sucky let's eat
everything gpu workloads.
-Daniel
--
Daniel Vetter
Mail: daniel@ffwll.ch
Mobile: +41 (0)79 365 57 48
next prev parent reply other threads:[~2012-06-04 19:53 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-02 16:08 [PATCH] radeon: Make PM info available to all, not just debug users Lauri Kasanen
2012-06-03 10:54 ` Christian König
2012-06-04 8:44 ` Lauri Kasanen
2012-06-04 11:30 ` Christian König
2012-06-04 12:30 ` Alex Deucher
2012-06-04 12:40 ` Martin Peres
2012-06-04 14:31 ` Jerome Glisse
2012-06-04 15:02 ` Martin Peres
2012-06-04 15:18 ` Jerome Glisse
2012-06-04 16:18 ` Christian König
2012-06-04 16:29 ` Lauri Kasanen
2012-06-04 17:05 ` Jerome Glisse
2012-06-05 10:11 ` Lauri Kasanen
2012-06-04 17:01 ` Martin Peres
2012-06-04 17:19 ` Jerome Glisse
2012-06-04 17:54 ` Martin Peres
2012-06-04 18:18 ` Jerome Glisse
2012-06-04 18:29 ` Jerome Glisse
2012-06-04 20:31 ` Martin Peres
2012-06-04 19:54 ` Daniel Vetter [this message]
2012-06-04 20:34 ` Martin Peres
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=20120604195433.GC29760@phenom.ffwll.local \
--to=daniel@ffwll.ch \
--cc=cand@gmx.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=j.glisse@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.