From: "H. Peter Anvin" <hpa@transmeta.com>
To: "Maciej W. Rozycki" <macro@ds2.pg.gda.pl>
Cc: Petr Vandrovec <vandrove@vc.cvut.cz>,
mingo@redhat.com, linux-kernel@vger.kernel.org, mikpe@csd.uu.se
Subject: Re: UP APIC reenabling vs. cpu type detection ordering
Date: Wed, 07 Feb 2001 10:00:01 -0800 [thread overview]
Message-ID: <3A818D21.6619FE3C@transmeta.com> (raw)
In-Reply-To: <Pine.GSO.3.96.1010207184159.1418E-100000@delta.ds2.pg.gda.pl>
"Maciej W. Rozycki" 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.
>
> It would be hard to decide how to classify it. It's something like "the
> CPU has a local APIC that we know how to handle in the non-MPS system".
>
> It might be viable just to delete the test altogether, though and just
> trap #GP(0) on the MSR access. For the sake of simplicity. If a problem
> with a system ever arizes, we may handle it then.
>
> Note that we still have to choose appropriate vendor-specific PeMo
> handling and an event for the NMI watchdog anyway.
>
Right... if that is the case then it seems reasonable.
-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/
prev parent reply other threads:[~2001-02-07 18:06 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
2001-02-07 17:55 ` Maciej W. Rozycki
2001-02-07 18:00 ` H. Peter Anvin [this message]
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=3A818D21.6619FE3C@transmeta.com \
--to=hpa@transmeta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=macro@ds2.pg.gda.pl \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox