GNOME Bugzilla – Bug 399461
Cpu-freq applet should permit to change governors silmutaneously on both cores of an intel core duo processor
Last modified: 2020-11-07 12:26:54 UTC
I suggest that one could place a single cpu-freq applet on its panel and change the governor simultaneously on both cores of an intel core duo processor. As of now, one must add 2 intances fo the applet to the panel (one for cpu-0 and one for cpu-1) and change each the applet separately. Other information:
Every applet instance represents a CPU, so I think it doesn't make sense that one applet can change the frequency of other CPU. In a core duo processor, when you change the frequency on any core, it's automatically changed in the other, so you can just add a single applet to monitor both cores. I'm going to close it as WONTFIX. Feel free to reopen it if you think I'm wrong.
Created attachment 81008 [details] Screenshot showing two instances with diff. frequencies
hmm, could you please give me the output of: $ ls -l /sys/devices/system/cpu/cpu1/ $ ls -l /sys/devices/system/cpu/cpu0
Here it is: nt271@constantines:~$ ls -l /sys/devices/system/cpu/cpu1/ total 0 drwxr-xr-x 5 root root 0 2007-01-23 14:08 cache drwxr-xr-x 3 root root 0 2007-01-23 18:43 cpufreq -r-------- 1 root root 4096 2007-01-23 13:00 crash_notes -rw------- 1 root root 4096 2007-01-23 13:00 online drwxr-xr-x 2 root root 0 2007-01-23 14:08 topology nt271@constantines:~$ ls -l /sys/devices/system/cpu/cpu0/ total 0 drwxr-xr-x 5 root root 0 2007-01-23 13:00 cache drwxr-xr-x 3 root root 0 2007-01-23 18:42 cpufreq -r-------- 1 root root 4096 2007-01-23 13:00 crash_notes drwxr-xr-x 2 root root 0 2007-01-23 13:00 topology By the way, I didn't know how to reopened this bug so I opened another one (Bug 399894) Nic
hmm, in my system cpufreq in cpu1 dir is a symlink to cpu0/cpufreq, I thought it was the same in every core duo system. Anyway, as I said, every applet instance represents a CPU and they don't know anything about other instances.
Exactly, but there is an easy way I think which would make the applet more usable and feel more up to date with the latest processors. Imagine that when you add one cpufreq applet and then you go in the list of cpus it can control it would list cpu0, cpu1, all. The two first would fonction normally as they do now. The "all" would fonction this way: It would set the frequencies to all the cpus previously recognized (it has a way to know the number of cpu already to populate the list). I mean instead of just changing the governor or freqs of cpu0 it would issue the command to cpu0 and cpu1. It could then monitor only one of these cpus since they would have the same settings anyway. I hear quad cores are coming out soon, there is no way someone can put 4 applets on their panel! Thanks for your help. regards, Nic
(In reply to comment #6) > Exactly, but there is an easy way I think which would make the applet more > usable and feel more up to date with the latest processors. Imagine that when > you add one cpufreq applet and then you go in the list of cpus it can control > it would list cpu0, cpu1, all. The problem is that this is the list of cpus to be monitored not to be handled. We would need to differentiate in some way what the applet is monitoring from what the applet is handling. > The two first would fonction normally as they > do now. The "all" would fonction this way: It would set the frequencies to > all the cpus previously recognized (it has a way to know the number of cpu > already to populate the list). I mean instead of just changing the governor or > freqs of cpu0 it would issue the command to cpu0 and cpu1. It could then > monitor only one of these cpus since they would have the same settings anyway. > > I hear quad cores are coming out soon, there is no way someone can put 4 > applets on their panel! > it sounds reasonable. Anyway, it can't be done right now because we are in feature and UI freeze time. I would like to know the opinion of usability guys too. > Thanks for your help. > Thank you for the feedback :-)
*** Bug 399894 has been marked as a duplicate of this bug. ***
any news? I think that this great feature should be implemented :)
Any update on this? Would be helpful indeed. Also there's an Ubuntu bug report about this at https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/408912
I, too, think that the cpufreq-applet should be made multicore-aware. The icon view could use a split bar to display the frequency for CPUs that support individual control of each core (AFAIK all Intel Core 2 and higher, and AMD starting with Socket AM2+). Attached is a "mock-up" of what I mean. This could save panel real estate compared to adding an icon for each core. The average user will probably want to control all cores at once, so there could be a configuation option like "Control each core individually", which is off by default.
Created attachment 141345 [details] Mock up how a single cpufreq-applet could display the speed of two cores
*** Bug 596047 has been marked as a duplicate of this bug. ***
I think Martins mock up would have problems for the case of 8+ cores. I'd suggest not to discriminate 'monitored' and 'handled' cores. Instead, how about letting people select not one core, but: - first half or - second half or - all cores For the single core case: leave out or ghost the first two options. For the dual core case the functionality is similar to what there is now, with the added value of the 'all cores' option which we all seem to want. For quad cores or more, the above proposition will keep the applet useful both for simple desktop users who just want to set all cores at once, but also for people who want to be able to set some high and some low. (in this the 8+ case I cannot think of any reason why one would want to target individual cores anyway) This will still allow people to put two applets in their task bar if they want, and select the different halves to have finer controls. And it's scalable with # of cores.
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all old feature requests in Bugzilla which have not seen updates for many years. If you still use gnome-applets and if you are still requesting this feature in a currently supported version of GNOME (currently that would be 3.38), then please feel free to report it at https://gitlab.gnome.org/GNOME/gnome-applets/-/issues/ Thank you for reporting this issue and we are sorry it could not be implemented.