On Wed, 2005-01-19 at 22:38 +0100, Dominik Brodowski wrote: > Currently, lock_cpu_hotplug serializes multiple calls to cpufreq->target() > on multiple CPUs even though that's unnecessary. Even further, it > serializes these calls with totally unrelated other parts of the kernel... > some ppc64 event reporting, some cache management, and so on. In my opinion > locking should be done subsystem (and normally data-)specific, and disabling > CPU hotplug should just do that.
Sure. Rusty. -- A bad analogy is like a leaky screwdriver -- Richard Braakman - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
