From: "J.A. Magallón" <jamagallon@ono.com>
To: Linux-Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Problems with -git14
Date: Wed, 30 Apr 2008 21:40:45 +0200 [thread overview]
Message-ID: <20080430214045.78c307d9@werewolf.home> (raw)
In-Reply-To: <Pine.LNX.4.64.0804301516580.30549@blonde.site>
On Wed, 30 Apr 2008 16:17:46 +0100 (BST), Hugh Dickins <hugh@veritas.com> wrote:
> On Wed, 30 Apr 2008, J.A. Magallón wrote:
> >
> > I have a couple problems with latest git (-14):
> >
> > - It only recognises 2 processors out of 4 (dual Xeon HT)
> [PATCH] x86_32: fix HT cpu booting
>
> Since recent smpboot 32/64-bit merge, my dual Xeon with HT has been
> booting only 2 of its 4 cpus (when running an i386 kernel; but x86_64
> is okay). J.A. Magallón reports the same.
>
> native_cpu_up: bad cpu 2
> native_cpu_up: bad cpu 3
>
> The mach-default cpu_present_to_apicid() was just returning cpu number
> (2, 3) instead of apicid (6, 7): looks like we now need the x86_64 code
> even for the i386 case.
>
One question that always bugs me: do I have to set NR_CPUS=8 to pick
apicid number 7, and let the map just flag the ones I have, or will
it work with NR_CPUS=4 ?
--
J.A. Magallon <jamagallon()ono!com> \ Software is like sex:
\ It's better when it's free
Mandriva Linux release 2008.1 (Cooker) for i586
Linux 2.6.23-jam05 (gcc 4.2.2 20071128 (4.2.2-2mdv2008.1)) SMP PREEMPT
next prev parent reply other threads:[~2008-04-30 19:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-29 23:56 Problems with -git14 J.A. Magallón
2008-04-30 15:17 ` Hugh Dickins
2008-04-29 17:22 ` Arjan van de Ven
2008-04-30 15:54 ` Glauber Costa
2008-05-05 7:13 ` Andrey Panin
2008-05-05 7:49 ` Thomas Gleixner
2008-04-30 18:13 ` Ingo Molnar
2008-04-30 18:27 ` Ingo Molnar
2008-04-30 19:40 ` J.A. Magallón [this message]
2008-05-01 12:04 ` Hugh Dickins
2008-05-01 0:50 ` J.A. Magallón
2008-05-01 12:11 ` Hugh Dickins
2008-05-02 1:41 ` Nick Piggin
2008-05-06 19:13 ` Jens Axboe
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=20080430214045.78c307d9@werewolf.home \
--to=jamagallon@ono.com \
--cc=linux-kernel@vger.kernel.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox