From: "H. Peter Anvin" <hpa@transmeta.com>
To: Mikael Pettersson <mikpe@csd.uu.se>
Cc: Petr Vandrovec <vandrove@vc.cvut.cz>,
mingo@redhat.com, linux-kernel@vger.kernel.org
Subject: Re: UP APIC reenabling vs. cpu type detection ordering
Date: Wed, 07 Feb 2001 09:43:21 -0800 [thread overview]
Message-ID: <3A818939.5BD3B740@transmeta.com> (raw)
In-Reply-To: <20010207135824.A24476@vana.vc.cvut.cz> <3A817F68.1A5C4EC1@transmeta.com> <14977.34686.377279.606313@harpo.it.uu.se>
Mikael Pettersson wrote:
>
> > In other words, I'd like to see a reason for making any vendor-specific
> > determinations, and if so, they should ideally be centralized to the CPU
> > feature-determination code.
>
> The Pentium 4 has a local APIC. It's not 100% compatible with the P6, and
> you sometimes have to know which one you're poking. CPUID returns the
> APIC feature bit. Should we mask its APIC capability? Of course not.
>
What's so "of course" about it? It mostly depends on how ugly the
determination is.
-hpa
--
<hpa@transmeta.com> at work, <hpa@zytor.com> in private!
"Unix gives you enough rope to shoot yourself in the foot."
http://www.zytor.com/~hpa/puzzle.txt
-
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-02-07 17:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-02-07 12:58 UP APIC reenabling vs. cpu type detection ordering Petr Vandrovec
2001-02-07 15:56 ` Maciej W. Rozycki
2001-02-07 17:01 ` H. Peter Anvin
2001-02-07 17:35 ` Mikael Pettersson
2001-02-07 17:43 ` H. Peter Anvin [this message]
2001-02-07 17:55 ` Maciej W. Rozycki
2001-02-07 18:00 ` H. Peter Anvin
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=3A818939.5BD3B740@transmeta.com \
--to=hpa@transmeta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mikpe@csd.uu.se \
--cc=mingo@redhat.com \
--cc=vandrove@vc.cvut.cz \
/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.