From: dann frazier <dannf@hp.com>
To: linux-ia64@vger.kernel.org
Subject: RE: cpu_to_node_map on UP systems
Date: Thu, 10 Mar 2005 17:19:45 +0000 [thread overview]
Message-ID: <1110475185.28015.26.camel@krebs.dannf> (raw)
In-Reply-To: <1110350919.9439.16.camel@localhost>
On Wed, 2005-03-09 at 11:31 -0800, Luck, Tony wrote:
> >> In 2.6.11, cpu_to_node_map has moved from numa.c to smpboot.c. Since
> >> smpboot.c isn't built on non-SMP systems, this causes
> >non-smp builds to
> >> fail to link in various places.
> >>
> >> I don't know what the right answer is here - resurrect numa.c maybe?
> >We do not seem to have a problem on our Autobuild with CONFIG_SMP=n
> >http://www.gelato.unsw.edu.au/kerncomp/
> >
> >Just tested latest bk ChangeSet@1.2028, 2005-03-08
> >16:26:54-08:00, gregkh@suse.de
> >tiger_defconfig
> >CONFIG_SMP=n
> >
> >plus removal of some unwanted drivers builds OK
>
> Yes, tiger builds ok with SMP=n (if you pull from the linux-ia64-test-2.6.12
> you'll also gets Bjorn's fix to iosapic so the the resulting kernel will
> boot, rather than hang).
>
> There are still problems with building the generic kernel with SMP=n
fyi, I tried a UP build of linux-ia64-test-2.6.12 (assuming I checked
out the right stuff - I don't use bk much), and I get the following
compile error:
AS arch/ia64/kernel/head.o
arch/ia64/kernel/head.S:267:54: macro
"SAL_TO_OS_BOOT_HANDOFF_STATE_SAVE" passed 3 arguments, but takes just 2
make[1]: *** [arch/ia64/kernel/head.o] Error 1
This is because the macro is defined as the following w/
CONFIG_HOTPLUG_CPU:
#define SAL_TO_OS_BOOT_HANDOFF_STATE_SAVE(_reg1,_reg2,_pred)
But, if CONFIG_HOTPLUG_CPU is disabled (it requires CONFIG_SMP), the
following is defined:
#define SAL_TO_OS_BOOT_HANDOFF_STATE_SAVE(a1,a2)
I posted my .config here:
http://free.linux.hp.com/~dannf/linux-ia64-test-2.6.12-20050310.config
next prev parent reply other threads:[~2005-03-10 17:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-09 6:48 cpu_to_node_map on UP systems dann frazier
2005-03-09 10:37 ` Darren Williams
2005-03-09 19:31 ` Luck, Tony
2005-03-09 22:21 ` Christoph Hellwig
2005-03-09 22:51 ` Jesse Barnes
2005-03-10 0:13 ` Luck, Tony
2005-03-10 1:28 ` Darren Williams
2005-03-10 17:19 ` dann frazier [this message]
2005-03-10 21:09 ` Luck, Tony
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=1110475185.28015.26.camel@krebs.dannf \
--to=dannf@hp.com \
--cc=linux-ia64@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