On Mon, Apr 24, 2006 at 12:38:35PM -0500, anoop aryal wrote: > On Monday 24 April 2006 12:13, you wrote: > > Hello! > > > > On Mon, Apr 24, 2006 at 01:51:09AM -0500, anoop aryal wrote: [...] > > But do really the Duo processor can swith frequencies independently for > > the 2 cores? > > Just for the records, could you send the output of cpufreq-info? > > it looks like it. at least under /sys there are cpu0 and cpu1 directories > with > what looks like independent settings. let me know if you want me to try
Yes, but it's the affected_cpus thing which matters here (as you already figured) > something specific to figure out for sure. > > ----------- cpufreq-info output > cpufrequtils 001: cpufreq-info (C) Dominik Brodowski 2004-2006 > Report errors and bugs to [EMAIL PROTECTED], please. > analyzing CPU 0: > driver: centrino > CPUs which need to switch frequency at the same time: 0 > hardware limits: 1000 MHz - 2.00 GHz > available frequency steps: 2.00 GHz, 1.67 GHz, 1.33 GHz, 1000 MHz > available cpufreq governors: ondemand, performance > current policy: frequency should be within 1000 MHz and 2.00 GHz. > The governor "ondemand" may decide which speed to use > within this range. > current CPU frequency is 1000 MHz (asserted by call to hardware). > analyzing CPU 1: > driver: centrino > CPUs which need to switch frequency at the same time: 1 > hardware limits: 1000 MHz - 2.00 GHz > available frequency steps: 2.00 GHz, 1.67 GHz, 1.33 GHz, 1000 MHz > available cpufreq governors: ondemand, performance > current policy: frequency should be within 1000 MHz and 2.00 GHz. > The governor "ondemand" may decide which speed to use > within this range. > current CPU frequency is 1000 MHz (asserted by call to hardware). > ----------- end cpufreq output > > i have had cpu0 in ondemand and cpu1 in performance before i tried fixing it. > so i guess you can do it independently. wow. Here's an small insight on the possibilities: http://marc.theaimsgroup.com/?l=linux-kernel&m=114308539123334&w=2 I think Duo's fall in case #2. [...] > ------- start > # cpufreq-info -a > 0 > -------- end > > prints just '0' by it's lonesome. does that mean that only cpu0 can be > changed? > > -------- start > # cpufreq-info --cpu 0 -a > 0 > #cpufreq-info --cpu 1 -a > 1 > -------- end [...] > i'm not sure it's related > but /sys/devices/system/cpu/cpu1/cpufreq/affected_cpus had '1' and the > corresponding file in cpu0 has '0' yes, that's what cpufreq-info reads :) > > for cpu in $(cpufreq-info -a | xargs echo) ; do given the above this line is not enough to loop through all available cpus. [...] > > Anyway the issue remains, can you test (and fix eventually :)) the code > > I provided? > > yeah. more than happy to do it for you. i'll try it in the evening and send > you the results. hmmm... don't bother to try it, it's clearly bugged. I'd say thing are getting too complex for such a stupid shell script. I'm thinking of some different approach: 1- provide per-cpu variables in /etc/defaults/cpufrequtils, eg: MAXFREQ0 MAXFREQ1 and so on or 2- provide a CPUS="0 1" variable in /etc/... to tell the script which cpus the user wants to change at boot time or 3- really implement that complex logic: read how many cpus (even an ls on /sys/devices/system/cpu/ could suffice) and for each cpu check if it has to be set (cpufreq-info -a -c $cpu) or if it was already affected by a previous change, based on that run cpufreq-set Ideas from a user perspective? > sorry about sending it twice. forgot to hit reply-to-all. don't worry, thanks for keeping the bug address :) Thanks -- mattia :wq! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
