From: Volker Armin Hemmann <volkerarmin@googlemail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Microcode update AMD
Date: Mon, 17 Jan 2011 20:14:16 +0100 [thread overview]
Message-ID: <4d34950a.0297df0a.5e61.ffffceff@mx.google.com> (raw)
In-Reply-To: <20110117183408.GG5748@solfire>
On Monday 17 January 2011 19:34:08 meino.cramer@gmx.de wrote:
> BRM <bm_witness@yahoo.com> [11-01-17 19:16]:
> > ----- Original Message ----
> >
> > > I have two questions:
> > > 1) Do I have to enable microcode updates in the BIOS of my
> > > Crosshair
> > >
> > > IV Formula to activate microcodes push in the CPU by the
> > > module
> > > "microcode" ? (AMD Phenom X6 1090T)
> >
> > Not sure about BIOS, but the Linux Kernel you are running will certainly
> > need support enabled too.
> >
> > > 2) Does anyone know, what these microcodes do? They are fixes
> > > for...
> > >
> > > ...what?
> >
> > The Intel and AMD processors are more abstract than physical now. With
> > i486 and earlier the processors were typically hard wired; hardware
> > "bug" fixes could not be pushed out.
even the 68000 used microcode...
> > Intel's Pentium (and I don't know which AMD) started using micro-code to
> > program the processor. This enabled them to push out "hardware" bug
> > fixes for the processors
sure that microcode was not introduced to x86 a lot earlier?
> >
> > So what happens is the x86 instruction (e.g. mov ax, bx) gets translated
> > to micro-code first, then it gets processed, and the result translated
> > back to the expected instruction result - essentially, emulating the
> > x86 instruction set in the processor. That's the simple version.
> >
> > So now when they discover a bug in the hardware they can push out a
> > micro-code update to either fix the "hardware" (microcode) bug or work
> > around a hardware (physical hardware) bug.
> >
> > Ben
>
> Hi Ben,
>
> thanks for your explanation...
> I meant: What is fixed the uc-patches? Does "mov" only except "17" as
> argument...or...
> I searched AMD for a changelog or something like but I ound nothing...
they never publish changelogs for microcode.
next prev parent reply other threads:[~2011-01-17 19:16 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-17 17:21 [gentoo-user] Microcode update AMD meino.cramer
2011-01-17 18:10 ` BRM
2011-01-17 18:34 ` meino.cramer
2011-01-17 19:14 ` Volker Armin Hemmann [this message]
2011-01-17 18:48 ` Mark Knecht
2011-01-17 19:12 ` Volker Armin Hemmann
2011-01-20 0:53 ` [gentoo-user] " walt
2011-01-20 1:08 ` walt
2011-01-17 19:08 ` [gentoo-user] " Volker Armin Hemmann
2011-01-17 19:19 ` meino.cramer
2011-01-17 19:46 ` Volker Armin Hemmann
2011-01-17 19:57 ` meino.cramer
2011-01-17 20:12 ` Mark Knecht
2011-01-17 20:52 ` Volker Armin Hemmann
2011-01-18 4:29 ` William Kenworthy
2011-01-18 15:38 ` Paul Hartman
2011-01-18 16:16 ` Mark Knecht
2011-01-18 17:34 ` Mark Knecht
2011-01-18 17:48 ` Volker Armin Hemmann
2011-02-05 14:28 ` Enrico Weigelt
2011-02-05 15:26 ` meino.cramer
2011-02-05 17:07 ` Volker Armin Hemmann
2011-02-06 11:36 ` Volker Armin Hemmann
2011-01-18 17:55 ` Paul Hartman
2011-01-18 18:21 ` Mark Knecht
2011-01-18 20:42 ` Paul Hartman
2011-01-18 20:56 ` Mick
2011-01-18 21:13 ` Paul Hartman
2011-01-18 23:08 ` Mick
2011-01-18 23:56 ` Mark Knecht
2011-01-17 20:13 ` Jason Weisberger
2011-01-17 20:49 ` Volker Armin Hemmann
2011-01-17 21:59 ` Jason Weisberger
2011-01-17 23:27 ` Volker Armin Hemmann
2011-01-18 15:39 ` [gentoo-user] " Nuno J. Silva
2011-02-05 13:34 ` [gentoo-user] " Enrico Weigelt
2011-02-05 16:15 ` Florian Philipp
2011-01-18 16:27 ` Volker Armin Hemmann
2011-01-19 17:10 ` Volker Armin Hemmann
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=4d34950a.0297df0a.5e61.ffffceff@mx.google.com \
--to=volkerarmin@googlemail.com \
--cc=gentoo-user@lists.gentoo.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