Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758294AbYHFFAU (ORCPT ); Wed, 6 Aug 2008 01:00:20 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1753761AbYHFEzS (ORCPT ); Wed, 6 Aug 2008 00:55:18 -0400 Received: from cn.fujitsu.com ([222.73.24.84]:53635 "EHLO song.cn.fujitsu.com" rhost-flags-OK-FAIL-OK-OK) by vger.kernel.org with ESMTP id S1752463AbYHFEzR (ORCPT ); Wed, 6 Aug 2008 00:55:17 -0400 Message-ID: <48992E5A.3050303@cn.fujitsu.com> Date: Wed, 06 Aug 2008 12:53:46 +0800 From: Li Zefan User-Agent: Thunderbird 2.0.0.9 (X11/20071115) MIME-Version: 1.0 To: Max Krasnyansky CC: Jeff Chua , lkml Subject: Re: 2.6.27rc1 cannot boot more than 8CPUs References: <48991B07.3050500@qualcomm.com> <48992085.3050203@qualcomm.com> <48992D35.9020005@qualcomm.com> In-Reply-To: <48992D35.9020005@qualcomm.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 898 Lines: 28 Max Krasnyansky wrote: > Jeff Chua wrote: >> On Wed, Aug 6, 2008 at 11:54 AM, Max Krasnyansky >> wrote: >> >>> Are you running 32-bit kernel ? >> >> Yes. But, does it matter? > > It used to. 64-bit kernel used to handle maxcpus option as documented in > the Documentation/cpu-hotplug.txt and 32-bit one was broken. > I just looked at the latest code and realized that both are now broken. > They ignore cpu id > maxcpus instead of not-booting them. > Yes. I have an x86_64 box with 4 cpus, but yesterday when I booted up with maxcpus=2, I didn't see the other 2 cpus. > I'll send a patch that fixes that tomorrow. > greate :) -- 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/