From: Danny van Dyk <kugelfang@gentoo.org>
To: richard.brunner@amd.com
Cc: ak@muc.de, linux-kernel@vger.kernel.org
Subject: Re: [RFC] Microcode Update Driver for AMD K8 CPUs
Date: Mon, 16 Aug 2004 14:57:37 +0200 [thread overview]
Message-ID: <4120AF41.4050400@gentoo.org> (raw)
In-Reply-To: <C2BC72CDFC11A44083B660CAC2E9EA67257333@SAUSEXMB1.amd.com>
richard.brunner@amd.com schrieb:
>>Danny van Dyk <kugelfang@gentoo.org> writes:
>>>I recently found some piece of code [1] to perform a microcode update
>>>on AMD's K8 CPUs. It included some update blocks hardcoded into the
>>>module.
>>Several people found this code (including me). But I don't think
>>it's a good idea right now to merge because it is better to leave
>>these things to the BIOS. It's unlikely that AMD will regularly
>>release "open" microcode updates anyways, and moving them
>>between BIOSes seems a bit dangerous to me (often you likely
>>need to change some magic MSRs too or you could have some
>>side effects). Overall it seems to be too dangerous to
>>do in a standard kernel.
>>Also I suspect the driver won't work very well on SMP.
>>-Andi
> As usual, Andi is absolutely correct.
> -Rich Brunner, AMD Fellow
Sigh. Well, that makes two *strong* votes against it.
Nevertheless, it's been a nice experience to work on that code.
Rich: Your CPUs are great ;-)
Andi: Can you explain to me, why you think that the module would not
work on SMP ? I don't know if this is still on topic: should we discuss
this off-list ? Vielleicht auf Deutsch *G ?
Danny
--
Danny van Dyk
Gentoo/AMD64 Developer
kugelfang@gentoo.org
next prev parent reply other threads:[~2004-08-16 12:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-16 1:24 [RFC] Microcode Update Driver for AMD K8 CPUs richard.brunner
2004-08-16 12:57 ` Danny van Dyk [this message]
[not found] <2tvqK-3rv-7@gated-at.bofh.it>
2004-08-15 20:58 ` Andi Kleen
-- strict thread matches above, loose matches on Subject: below --
2004-08-15 15:48 Danny van Dyk
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=4120AF41.4050400@gentoo.org \
--to=kugelfang@gentoo.org \
--cc=ak@muc.de \
--cc=linux-kernel@vger.kernel.org \
--cc=richard.brunner@amd.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox