Hi! > >> >> > I guess better interface would be something like > >> >> > > >> >> > pstate/07/core_clock_min > >> >> > core_clock_max > >> >> > memory_clock_min > >> >> > memory_clock_max > >> >> > > >> >> > and then pstate/active containing just the number of active state? > > > >> Could we just say that the format of this file is one-per-line of > >> > >> level: information-for-the-user > > > > But it is not. > > But it is... > > > Management tools will want to parse it, sooner or > > later. What is wrong with solution described above? > > It is complex and annoying to the people that will actually use it. grep -r . pstate/ is actually not that bad... And yes, some kind of utility to select right performance level would be nice in future... Or maybe not. Perhaps in not so distant future kernel will use right performance level for given load...? Pavel -- (english) http://www.livejournal.com/~pavelmachek (cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html _______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
