From: David Woodhouse <dwmw2@infradead.org>
To: Ingo Molnar <mingo@redhat.com>
Cc: Alan Cox <alan@lxorguk.ukuu.org.uk>,
Keith Owens <kaos@ocs.com.au>,
Nathan Walp <faceprint@faceprint.com>,
Hans Grobler <grobh@sun.ac.za>,
linux-kernel@vger.kernel.org
Subject: Re: Oops in 2.4.0-ac5
Date: Thu, 11 Jan 2001 11:15:55 +0000 [thread overview]
Message-ID: <1605.979211755@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.30.0101101737240.30973-100000@devserv.devel.redhat.com>
In-Reply-To: <Pine.LNX.4.30.0101101737240.30973-100000@devserv.devel.redhat.com>
mingo@redhat.com said:
> i prefer clear oopses and bug reports instead of ignoring them. A
> failed MSR write is not something to be taken easily. MSR writes if
> fail mean that there is a serious kernel bug - we want to stop the
> kernel and complain ASAP. And correct code will be much more readable
> that way.
The bug here seems to be that we're using the same bit (X86_FEATURE_APIC) to
report two _different_ features.
We don't represent X86_FEATURE_CXMMX and X86_FEATURE_MMX with the same bit,
even though they are supposed to provide the same functionality - because
they are in fact different. Likewise we shouldn't use the same bit for the
two different types of APIC, IMO.
Index: include/asm-i386/cpufeature.h
===================================================================
RCS file: /inst/cvs/linux/include/asm-i386/Attic/cpufeature.h,v
retrieving revision 1.1.2.1
diff -u -r1.1.2.1 cpufeature.h
--- include/asm-i386/cpufeature.h 2000/12/05 13:30:46 1.1.2.1
+++ include/asm-i386/cpufeature.h 2001/01/11 11:12:41
@@ -62,6 +62,7 @@
#define X86_FEATURE_K6_MTRR (3*32+ 1) /* AMD K6 nonstandard MTRRs */
#define X86_FEATURE_CYRIX_ARR (3*32+ 2) /* Cyrix ARRs (= MTRRs) */
#define X86_FEATURE_CENTAUR_MCR (3*32+ 3) /* Centaur MCRs (= MTRRs) */
+#define X86_FEATURE_AMD_APIC (3*32+ 4) /* AMD Athlon CPU-local APIC */
#endif /* __ASM_I386_CPUFEATURE_H */
Index: arch/i386/kernel/setup.c
===================================================================
RCS file: /inst/cvs/linux/arch/i386/kernel/setup.c,v
retrieving revision 1.4.2.47
diff -u -r1.4.2.47 setup.c
--- arch/i386/kernel/setup.c 2001/01/01 12:56:13 1.4.2.47
+++ arch/i386/kernel/setup.c 2001/01/11 11:12:41
@@ -1058,6 +1058,11 @@
break;
case 6: /* An Athlon/Duron. We can trust the BIOS probably */
+ if (test_bit(X86_FEATURE_APIC, &c->x86_capability)) {
+ /* Not a compatible APIC */
+ clear_bit(X86_FEATURE_APIC, &c->x86_capability);
+ set_bit(X86_FEATURE_AMD_APIC, &c->x86_capability);
+ }
break;
}
--
dwmw2
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-11 11:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-10 20:00 Oops in 2.4.0-ac5 Nathan Walp
2001-01-10 20:17 ` Hans Grobler
2001-01-10 20:23 ` Nathan Walp
2001-01-10 20:48 ` Hans Grobler
2001-01-10 21:00 ` Nathan Walp
2001-01-10 22:29 ` Keith Owens
2001-01-10 22:37 ` Alan Cox
2001-01-10 22:41 ` Ingo Molnar
2001-01-11 11:15 ` David Woodhouse [this message]
2001-01-11 11:41 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2001-01-11 12:56 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=1605.979211755@redhat.com \
--to=dwmw2@infradead.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=faceprint@faceprint.com \
--cc=grobh@sun.ac.za \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--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 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.