On 24 March 2013 14:35, Thomas Renninger <trenn@xxxxxxx> wrote: > I take that back. > CPU hot-add (even if CPU is not present at boot time) works. > I looked at C-states for that some time ago and it should only work if > the hot-add event came in via ACPI events for CPUs which were not > initialized at boot time. Better would be to initialize the first time it > gets switched online. I removed it from my TODO list, thanks :) > Anyway, making such stuff (cpufreq/cpuidle/...) more robust, > is certainly a good idea. Yes, that was the basic intent of my earlier patches that went into 3.9. It was all about simplifying it and making it robust. > And powernow-k8 does not exist anymore..., fortunately I didn't have to > look at this stuff for some time. Sure? Driver is still present in mainline. BTW, i have given an initial fix for acpi-cpufreq (which should work) and waiting for Duncan to reply back. All other drivers don't set affected/related cpus directly, so they should be alright. -- viresh -- 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
