From: "H. Peter Anvin" <hpa@zytor.com>
To: linux-kernel@vger.kernel.org
Subject: Re: [patch-2.4.0-test12-pre3] microcode update for P4 (fwd)
Date: 1 Dec 2000 21:29:46 -0800 [thread overview]
Message-ID: <90a1ca$3rt$1@cesium.transmeta.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0012011150490.877-100000@penguin.homenet>
Followup to: <Pine.LNX.4.21.0012011150490.877-100000@penguin.homenet>
By author: Tigran Aivazian <tigran@veritas.com>
In newsgroup: linux.dev.kernel
>
> Second attempt -- the first one got lost due to some local mail client
> problems...
>
> Hi Linus,
>
> Here is the patch to microcode update driver to support the new P4
> CPU.
>
> --- linux/include/asm-i386/msr.h Thu Oct 7 18:17:09 1999
> +++ ucode/include/asm-i386/msr.h Fri Dec 1 09:38:59 2000
> @@ -30,3 +30,7 @@
> : "=a" (low), "=d" (high) \
> : "c" (counter))
>
> +/* symbolic names for some interesting MSRs */
> +#define IA32_PLATFORM_ID 0x17
> +#define IA32_UCODE_WRITE 0x79
> +#define IA32_UCODE_REV 0x8B
>
Please call these MSR_* instead, "IA32_*" isn't very descriptive,
besides, the preferred prefix in existing locations in the Linux
kernel is "X86_", e.g. X86_EFLAGS_IF or X86_CR4_PSE. I think there
are standard symbolic names for most MSRs in volume 3 of the Intel
processor manuals; I would suggest we use those.
-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:[~2000-12-02 6:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-01 11:51 [patch-2.4.0-test12-pre3] microcode update for P4 (fwd) Tigran Aivazian
2000-12-02 5:29 ` H. Peter Anvin [this message]
2000-12-02 13:08 ` Alan Cox
2000-12-02 20:25 ` H. Peter Anvin
2000-12-02 14:11 ` Tigran Aivazian
[not found] <Pine.LNX.4.21.0012022049430.933-100000@penguin.homenet>
2000-12-02 20:57 ` H. Peter Anvin
[not found] <Pine.LNX.4.21.0012022103290.933-100000@penguin.homenet>
2000-12-02 21:10 ` H. Peter Anvin
[not found] <Pine.LNX.4.21.0012022111350.933-100000@penguin.homenet>
2000-12-02 21:26 ` H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2000-12-02 22:11 Tigran Aivazian
2000-12-03 15:45 ` Matti Aarnio
2000-12-03 16:03 ` Tigran Aivazian
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='90a1ca$3rt$1@cesium.transmeta.com' \
--to=hpa@zytor.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox