2009/9/17 Rafał Miłecki <[email protected]>
> W dniu 18 września 2009 00:55 użytkownik Rafał Miłecki
> <[email protected]> napisał:
> > My new proposition is rather create some "user_power_mode" and let
> > user specify all 3 params. For example:
> > $ echo 200000 400000 1050 > /sys/class/gpu/user_power_mode
> > $ cat /sys/class/gpu/user_power_mode
> > Engine clock: 200000
> > Memory clock: 400000
> > Voltage: 1050
>
> Or maybe
> $ echo user 200000 400000 1050 > /sys/class/gpu/power_modes
> $ echo minimum 100000 200000 900 > /sys/class/gpu/power_modes
> do you think we should allow user to overwrite all modes?
>
> --
> Rafał
>
>
What about multi-gpu systems? I think we want to expose this interface as
gpu specific location.
I agree that user-space interface should have atomic way of setting all
parameters at once. But I think that at first we want to only expose some
predefined states to user-space that are known to work well in some
workloads. This will make it easier to track down bugs in power management
code when there is not so many variables in play.
Of course later it would be nice to give more control to user-space so user
can control voltages and clocks manually (for example overclockers would
like this kind of feature).
I also think that there should be logging for all power state changes so it
is easier to know what went wrong if just looking the dmesg that user
provided when reporting the bug.
So maybe it is best to develop complete idea of interface at first for
developer testing and only exposes simple interface to users at first and
later expose full control interface.
Pauli
------------------------------------------------------------------------------
Come build with us! The BlackBerry® Developer Conference in SF, CA
is the only developer event you need to attend this year. Jumpstart your
developing skills, take BlackBerry mobile applications to market and stay
ahead of the curve. Join us from November 9-12, 2009. Register now!
http://p.sf.net/sfu/devconf
--
_______________________________________________
Dri-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dri-devel
