Message-ID: <40796318.4010508@yahoo.com.au>
Date: Mon, 12 Apr 2004 01:24:08 +1000
From: Nick Piggin <nickpiggin@yahoo.com.au>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040122 Debian/1.6-1
MIME-Version: 1.0
To: "Martin J. Bligh" <mbligh@aracnet.com>
CC: linux-kernel <linux-kernel@vger.kernel.org>
Subject: Re: scheduler problems on shutdown
References: <1516092704.1081534916@[10.10.2.4]> <71390000.1081611090@[10.10.2.4]> <40791475.7040300@cyberone.com.au> <1860000.1081696302@[10.10.2.4]>
In-Reply-To: <1860000.1081696302@[10.10.2.4]>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 918
Lines: 28

Martin J. Bligh wrote:
>>I think the WARN_ON can go. You have to make sure the for_each_cpu
>>loop doesn't get to run it though. It shouldn't be in the latest -mm
>>kernels, is it?
> 
> 
> OK, I'll figure it out. I don't like the latest code, so don't really want
> to "upgrade" though.
>  

Oh? Anything specific?

> 
>>It is normal to have an entire group offline with CPU hotplug.
> 
> 
> Only if we can't figure out how to hotplug groups as well, which would
> be a much cleaner way of doing it.
> 

I think we'll soon want to add a sched domain setup callback
for hotplug that can take care of these things as required.
But for now, the current situation should be OK.
-
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/