http://bugzilla.novell.com/show_bug.cgi?id=530035 User pgnet.dev@gmail.com added comment http://bugzilla.novell.com/show_bug.cgi?id=530035#c4 --- Comment #4 from pgnet Dev <pgnet.dev@gmail.com> 2009-08-19 10:03:19 MDT --- (In reply to comment #3)
Just to clarify: The governors other than on-demand are (even in -unstable) only supported/used on Intel CPUs (using the generic ACPI cpufreq driver). The PowerNow! driver is hardwired to the on-demand governor. I don't think we're going to fix this on our own - we'll want AMD to adjust their code (Joachim, could you find out if there are any plans to do so, and if so, when to expect functional code in -unstable?), and only then we can consider backporting it.
PowerNow's _hardwired_ to a single governor ?! Then, you're a better sleuth than I ... where on earth did you find that fact documented? I've clearly missed it :-/ Wholly agree that if it _is_ the case, then it should be an upstream fix. I'm not clear what effect, if any, the cpufreq=xen:ondemand(or performance) in grub's having ... is it simply being ignored in the PowerNow case? Even if so, that still leaves items (1) & (2) as issues ... or, perhaps _all_ of this depends on AMD fixes? I'll happily retest the above behaviors once that's in place. p.s. I don't think "RESOLVED:FEATURE" is wholly appropriate here -- as the goal needs to be "works consistently with Xen's features and across CPUs", but not clear how ELSE one would categorize other than to leave OPEN ... -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.