On Mon, Dec 5, 2011 at 7:00 PM, chao xie <xiechao.linux@xxxxxxxxx> wrote: > Hi > The CPUFreq ondemand governor will use deferrable timer for cpu > workload profiling. > The deferrable timer will not invoke the core when the core is totally idle. > So for a SMP system, there are two cores, each one will have its own > cpufreq_policy and do the profiling and change the frequency of core. > I find that after system boot up, and I set the governor of the two > cores to be “ondemand”. The profiling in CPU1 will never start because > CPU1 is in idle, and the deferrable timer cpu profiling depends on > will not wake up core. > Is that a problem, or I made mistake about how to set up cpufreq in > the SMP system? If CPU1 is in idle indefinitely, why is not having CPU1 profiled a problem? If CPU1 is not used, you don't need to profile and adjust the frequency of CPU1 either, do you? MyungJoo > -- > 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 -- MyungJoo Ham, Ph.D. Mobile Software Platform Lab, DMC Business, Samsung Electronics -- 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
