mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Mikael Pettersson <mikpe@csd.uu.se>
To: alan@lxorguk.ukuu.org.uk
Cc: linux-kernel@vger.kernel.org, macro@ds2.pg.gda.pl, mingo@redhat.com
Subject: [PATCH] UP-APIC fix for Mobile P6
Date: Thu, 8 Mar 2001 23:55:33 +0100 (MET)	[thread overview]
Message-ID: <200103082255.XAA14402@harpo.it.uu.se> (raw)

Alan et al,

This patch (against 2.4.2-ac14) fixes a buglet in the UP-APIC support.
As a side-effect of hpa's CPU detection rewrite in 2.4.0-test, the
X86_FEATURE constants where changed from bit masks to bit numbers.
Unfortunately one spot in apic.c:detect_init_APIC() wasn't updated,
with the effect that we would fail to detect P6 processors lacking
local APICs (all Mobile P6 CPUs it seems).

This didn't cause failures in the NMI watchdog since the new detection
code in setup.c would clear the APIC feature bit before any damage
was done. However, some users were confused by the fact that their
kernels would claim to have detected and initialised the local APIC,
but still the NMI watchdog wouldn't run.

/Mikael

--- linux-2.4.2-ac14/arch/i386/kernel/apic.c.~1~	Thu Mar  8 22:18:04 2001
+++ linux-2.4.2-ac14/arch/i386/kernel/apic.c	Thu Mar  8 22:31:49 2001
@@ -548,7 +548,7 @@
 
 static int __init detect_init_APIC (void)
 {
-	u32 h, l, dummy, features;
+	u32 h, l, features;
 	int needs_pm = 0;
 	extern void get_cpu_vendor(struct cpuinfo_x86*);
 
@@ -588,8 +588,8 @@
 	 * The APIC feature bit should now be enabled
 	 * in `cpuid'
 	 */
-	cpuid(1, &dummy, &dummy, &dummy, &features);
-	if (!(features & X86_FEATURE_APIC)) {
+	features = cpuid_edx(1);
+	if (!(features & (1 << X86_FEATURE_APIC))) {
 		printk("Could not enable APIC!\n");
 		return -1;
 	}

                 reply	other threads:[~2001-03-08 22:56 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=200103082255.XAA14402@harpo.it.uu.se \
    --to=mikpe@csd.uu.se \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macro@ds2.pg.gda.pl \
    --cc=mingo@redhat.com \
    /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

all inboxes | Powered by JetHome®