From: Andi Kleen <ak@suse.de>
To: torvalds@osdl.org
Cc: linux-kernel@vger.kernel.org
Subject: [PATCH] Fix microcode change for i386
Date: Thu, 19 Feb 2004 01:11:59 +0100 [thread overview]
Message-ID: <20040219011159.6f60aa69.ak@suse.de> (raw)
This patch should fix the i386 compile problem in the microcode driver I caused with
the IA32e updates.
diff -u linux-2.6.3-amd64/arch/i386/kernel/microcode.c-o linux-2.6.3-amd64/arch/i386/kernel/microcode.c
--- linux-2.6.3-amd64/arch/i386/kernel/microcode.c-o 2004-02-19 00:19:32.000000000 +0100
+++ linux-2.6.3-amd64/arch/i386/kernel/microcode.c 2004-02-19 00:56:41.000000000 +0100
@@ -371,8 +371,8 @@
spin_lock_irqsave(µcode_update_lock, flags);
/* write microcode via MSR 0x79 */
- wrmsr(MSR_IA32_UCODE_WRITE, (u64)(uci->mc->bits),
- (u64)(uci->mc->bits) >> 32);
+ wrmsr(MSR_IA32_UCODE_WRITE, (u32)(unsigned long)(uci->mc->bits),
+ (u32)(((unsigned long)uci->mc->bits) >> 32));
wrmsr(MSR_IA32_UCODE_REV, 0, 0);
__asm__ __volatile__ ("cpuid" : : : "ax", "bx", "cx", "dx");
next reply other threads:[~2004-02-18 23:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-19 0:11 Andi Kleen [this message]
2004-02-18 23:29 ` [PATCH] Fix microcode change for i386 Linus Torvalds
2004-02-19 5:16 ` Jeff Garzik
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=20040219011159.6f60aa69.ak@suse.de \
--to=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@osdl.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