From: "Randy.Dunlap" <rddunlap@osdl.org>
To: Dave Jones <davej@suse.de>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] AMD SMP capability sanity checking.
Date: Fri, 16 Nov 2001 13:41:12 -0800 [thread overview]
Message-ID: <3BF587F8.84607648@osdl.org> (raw)
In-Reply-To: <Pine.LNX.4.30.0111162219170.22827-100000@Appserv.suse.de>
Dave-
A couple of minor comments below.
~Randy
Dave Jones wrote:
>
> Note, this code will not stop you from continuing to use unsupported
> configurations, but will..
> a. Print a boot time warning.
> b. Taint any oopses so that SMP problem oopses can be isolated easily.
>
> I repeat, there is *no* loss of functionality.
>
> Patch against 2.4.15pre5 follows.
>
> diff -urN --exclude-from=/home/davej/.exclude linux-2.4.15-pre5/arch/i386/kernel/smpboot.c linux-2.4.15-pre5-dj/arch/i386/kernel/smpboot.c
> --- linux-2.4.15-pre5/arch/i386/kernel/smpboot.c Fri Oct 5 01:42:54 2001
> +++ linux-2.4.15-pre5-dj/arch/i386/kernel/smpboot.c Fri Nov 16 21:09:33 2001
> + printk (KERN_INFO "WARNING: This combination of AMD processors is not suitable for SMP.\n");
> + tainted |= (1<<2);
Some bit #defines for <tainted> would be nice (instead of magic
numbers).
> diff -urN --exclude-from=/home/davej/.exclude linux-2.4.15-pre5/kernel/panic.c linux-2.4.15-pre5-dj/kernel/panic.c
> --- linux-2.4.15-pre5/kernel/panic.c Sun Sep 30 19:26:08 2001
> +++ linux-2.4.15-pre5-dj/kernel/panic.c Fri Nov 16 20:46:17 2001
> @@ -103,6 +103,10 @@
> /**
> * print_tainted - return a string to represent the kernel taint state.
> *
> + * 'P' - Proprietory module has been loaded.
> + * 'F' - Module has been forcibly loaded.
> + * 'S' - SMP with CPUs not designed for SMP.
> + *
> * The string is overwritten by the next call to print_taint().
> */
>
> @@ -112,7 +116,8 @@
> if (tainted) {
> snprintf(buf, sizeof(buf), "Tainted: %c%c",
>>>>>>>>>>>>>>>>>> %c%c%c <<<<<<<<<<<<<
> tainted & 1 ? 'P' : 'G',
> - tainted & 2 ? 'F' : ' ');
> + tainted & 2 ? 'F' : ' ',
> + tainted & 4 ? 'S' : ' ');
> }
> else
> snprintf(buf, sizeof(buf), "Not tainted");
next prev parent reply other threads:[~2001-11-16 21:43 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-16 21:30 [PATCH] AMD SMP capability sanity checking Dave Jones
2001-11-16 19:42 ` Gérard Roudier
2001-11-16 21:41 ` Randy.Dunlap [this message]
2001-11-16 21:46 ` Dave Jones
2001-11-16 21:44 ` Dan Hollis
2001-11-16 22:02 ` Dave Jones
2001-11-16 21:46 ` Jeff Garzik
2001-11-16 21:59 ` Stefan Smietanowski
2001-11-16 22:11 ` Dave Jones
2001-11-16 22:37 ` Jeff Golds
2001-11-16 23:04 ` Dave Jones
2001-11-17 0:33 ` Jeff Golds
2001-11-17 0:39 ` Dave Jones
2001-11-17 0:59 ` Andreas Boman
2001-11-17 1:54 ` Mike Fedyk
2001-11-17 4:11 ` Nathan Walp
2001-11-17 4:59 ` Mark Orr
2001-11-16 23:40 ` Stefan Smietanowski
2001-11-16 23:47 ` Dave Jones
2001-11-17 1:05 ` Stefan Smietanowski
2001-11-17 1:09 ` Dan Hollis
2001-11-17 1:11 ` Dave Jones
2001-11-17 1:10 ` Dave Jones
2001-11-21 0:42 ` Pavel Machek
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=3BF587F8.84607648@osdl.org \
--to=rddunlap@osdl.org \
--cc=davej@suse.de \
--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 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.