From: Gerd Hoffmann <kraxel@suse.de>
To: Rene Herman <rene.herman@keyaccess.nl>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: [patch] SMP alternatives: skip with UP kernels.
Date: Thu, 11 May 2006 14:13:22 +0200 [thread overview]
Message-ID: <44632A62.2020505@suse.de> (raw)
In-Reply-To: <4461D16A.3000301@keyaccess.nl>
[-- Attachment #1: Type: text/plain, Size: 391 bytes --]
> Okay, thanks. Yes, I agree such would make sense.
Patch below. It simply returns in case the tables are empty and nothing
is do to, thus avoids printing the confusing message.
cheers,
Gerd
--
Gerd Hoffmann <kraxel@suse.de>
Erst mal heiraten, ein, zwei Kinder, und wenn alles läuft
geh' ich nach drei Jahren mit der Familie an die Börse.
http://www.suse.de/~kraxel/julika-dora.jpeg
[-- Attachment #2: ifdef-smp-alts --]
[-- Type: text/plain, Size: 641 bytes --]
Index: vanilla-2.6.17-rc3-mm1/arch/i386/kernel/alternative.c
===================================================================
--- vanilla-2.6.17-rc3-mm1.orig/arch/i386/kernel/alternative.c 2006-05-10 12:25:39.000000000 +0200
+++ vanilla-2.6.17-rc3-mm1/arch/i386/kernel/alternative.c 2006-05-10 15:00:10.000000000 +0200
@@ -349,6 +349,9 @@ void __init alternative_instructions(voi
smp_alt_once = 1;
#endif
+ if (0 == (__smp_alt_end - __smp_alt_begin))
+ return; /* no tables, nothing to patch (UP kernel) */
+
if (smp_alt_once) {
if (1 == num_possible_cpus()) {
printk(KERN_INFO "SMP alternatives: switching to UP code\n");
next prev parent reply other threads:[~2006-05-11 12:11 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-10 0:30 2.6.17-rc3 -- SMP alternatives: switching to UP code Rene Herman
2006-05-10 1:55 ` Chase Venters
2006-05-10 9:28 ` Gerd Hoffmann
2006-05-10 11:41 ` Rene Herman
2006-05-11 12:13 ` Gerd Hoffmann [this message]
2006-05-11 21:07 ` [patch] SMP alternatives: skip with UP kernels Rene Herman
2006-05-12 11:41 ` Gerd Hoffmann
2006-05-15 21:41 ` Rene Herman
-- strict thread matches above, loose matches on Subject: below --
2006-05-11 16:22 Mikael Pettersson
2006-05-11 18:28 ` Andi Kleen
2006-05-11 21:18 Mikael Pettersson
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=44632A62.2020505@suse.de \
--to=kraxel@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rene.herman@keyaccess.nl \
/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.