On 27 May 2013 05:50, karthik vm <meetvm@xxxxxxxxx> wrote: > Thanks for your insights Viresh & Dirk. I really appreciate it. > > I read from the net that the p-state (Voltage/Frequency) pairs in > Intel processors(e.g Nehalem) cannot be set for individual cores > (http://web.archive.org/web/20130527001342/http://people.cs.pitt.edu/~kirk/cs3150spring2010/ShiminChen.pptx). I don't really know how much we can trust this one.. > As Dirk pointed out, each core may request a p-state but ultimately > all the whole processor's p-state is set to the minimum of the > requested p-states. But in my Core2Duo processor, I see that two cores > are in different frequencies(p-state) and it did not fit into the > explanation above :-(. I think I am missing something. How do you see that? cpufreq-info? That can be tricky as the cpufreq driver might not have exposed this to core.. So, core thinks cores can run at separate frequencies but code in driver is taking care to pass on the minimum of all cores to h/w. -- To unsubscribe from this list: send the line "unsubscribe cpufreq" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
