From: William Lee Irwin III <wli@holomorphy.com>
To: linux-kernel@vger.kernel.org
Cc: rml@tech9.net
Subject: NUMA-Q breakage 7/7 preempt vs. printk bootstrap ordering
Date: Fri, 12 Jul 2002 15:40:16 -0700 [thread overview]
Message-ID: <20020712224016.GE25360@holomorphy.com> (raw)
CONFIG_PREEMPT creates a bootstrap ordering issue as some implicit
scheduling done in printk.c raises exceptions prior to the secondary
cpus being prepared to handle them (seen as no vm86_info: BAD).
The workaround, enclosed below is not to use preempt on NUMA-Q.
Cheers,
Bill
===== arch/i386/config.in 1.40 vs edited =====
--- 1.40/arch/i386/config.in Mon Jun 17 07:03:16 2002
+++ edited/arch/i386/config.in Fri Jul 12 01:12:25 2002
@@ -165,7 +165,9 @@
define_bool CONFIG_X86_IO_APIC y
fi
else
- bool 'Multiquad NUMA system' CONFIG_MULTIQUAD
+ if [ "$CONFIG_PREEMPT" != "y" ]; then
+ bool 'Multiquad NUMA system' CONFIG_MULTIQUAD
+ fi
fi
bool 'Machine Check Exception' CONFIG_X86_MCE
reply other threads:[~2002-07-12 22:39 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020712224016.GE25360@holomorphy.com \
--to=wli@holomorphy.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rml@tech9.net \
/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