From: Li Zefan <lizf@cn.fujitsu.com>
To: Max Krasnyansky <maxk@qualcomm.com>
Cc: Jeff Chua <jeff.chua.linux@gmail.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.27rc1 cannot boot more than 8CPUs
Date: Wed, 06 Aug 2008 12:53:46 +0800 [thread overview]
Message-ID: <48992E5A.3050303@cn.fujitsu.com> (raw)
In-Reply-To: <48992D35.9020005@qualcomm.com>
Max Krasnyansky wrote:
> Jeff Chua wrote:
>> On Wed, Aug 6, 2008 at 11:54 AM, Max Krasnyansky <maxk@qualcomm.com>
>> 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 :)
next prev parent reply other threads:[~2008-08-06 5:00 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-06 3:15 2.6.27rc1 cannot boot more than 8CPUs Jeff Chua
2008-08-06 3:31 ` Max Krasnyansky
2008-08-06 3:50 ` Jeff Chua
2008-08-06 3:54 ` Max Krasnyansky
2008-08-06 4:06 ` Jeff Chua
2008-08-06 4:48 ` Max Krasnyansky
2008-08-06 4:53 ` Li Zefan [this message]
2008-08-06 20:11 ` Max Krasnyansky
[not found] ` <86802c440808052050u489264beo30812523669ef4df@mail.gmail.com>
2008-08-06 4:05 ` Jeff Chua
2008-08-06 5:19 ` David Miller
2008-08-06 6:42 ` Jeff Chua
2008-08-06 7:18 ` David Miller
2008-08-06 9:33 ` Jeff Chua
2008-08-06 9:36 ` David Miller
2008-08-06 9:50 ` Jeff Chua
2008-08-06 8:49 ` Yinghai Lu
2008-08-06 9:35 ` Jeff Chua
2008-08-06 9:42 ` Jeff Chua
2008-08-06 6:01 ` Linus Torvalds
2008-08-06 6:42 ` Jeff Chua
2008-08-06 15:33 ` Jeff Chua
2008-08-11 19:59 ` Ingo Molnar
2008-08-11 20:03 ` Yinghai Lu
2008-08-11 20:08 ` Ingo Molnar
2008-08-11 20:12 ` Yinghai Lu
2008-08-11 20:36 ` Yinghai Lu
2008-08-11 20:44 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2008-08-06 11:09 Jeff Chua
2008-08-06 16:13 ` Yinghai Lu
2008-08-06 16:34 ` Jeff Chua
2008-08-11 19:54 ` Ingo Molnar
2008-08-13 14:16 ` Ingo Molnar
2008-08-13 17:10 ` Jeff Chua
2008-08-13 17:33 ` Jeff Chua
2008-08-13 17:39 ` Ingo Molnar
2008-08-13 17:46 ` Yinghai Lu
2008-08-13 18:33 ` Yinghai Lu
2008-08-14 7:16 ` Jeff Chua
2008-08-14 8:59 ` Yinghai Lu
2008-08-14 9:07 ` Ingo Molnar
2008-08-15 10:34 Jeff Chua
2008-08-15 14:07 ` Ingo Molnar
2008-08-18 3:07 ` Jeff Chua
2008-08-18 8:00 ` Ingo Molnar
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48992E5A.3050303@cn.fujitsu.com \
--to=lizf@cn.fujitsu.com \
--cc=jeff.chua.linux@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maxk@qualcomm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.