Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755503AbYGOEEy (ORCPT ); Tue, 15 Jul 2008 00:04:54 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1750865AbYGOEEq (ORCPT ); Tue, 15 Jul 2008 00:04:46 -0400 Received: from smtp1.linux-foundation.org ([140.211.169.13]:37549 "EHLO smtp1.linux-foundation.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1750814AbYGOEEq (ORCPT ); Tue, 15 Jul 2008 00:04:46 -0400 Date: Mon, 14 Jul 2008 21:04:12 -0700 (PDT) From: Linus Torvalds To: Steven Rostedt cc: Dmitry Adamushko , Vegard Nossum , Paul Menage , Max Krasnyansky , Paul Jackson , Peter Zijlstra , miaox@cn.fujitsu.com, Thomas Gleixner , Ingo Molnar , Linux Kernel Subject: Re: current linux-2.6.git: cpusets completely broken In-Reply-To: Message-ID: References: <20080712031736.GA3040@damson.getinternet.no> User-Agent: Alpine 1.10 (LFD 962 2008-03-14) MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 913 Lines: 23 On Mon, 14 Jul 2008, Steven Rostedt wrote: > > Oh, I'm not arguing. My mind is going off to an even bigger picture, where > something in the future would need to stop migration to a particular CPU, > and that it could simply clear the bit and call synchronize_sched. The run > queue lock is only visible to the scheduler. Sorry, I may have been day > dreaming out loud ;-) Well, you'd be stuck right now anyway. At least in my trivial patch, the cpu_active_map locking is protected by 'cpu_add_remove_lock' which is static to cpu.c. The only thing that modifies it (apart from the initial setup before SMP has been brought up) is the hotplug code. Linus -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/