From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1PeuZG-0005SN-V0 for garchives@archives.gentoo.org; Mon, 17 Jan 2011 19:16:46 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id F3246E0138; Mon, 17 Jan 2011 19:14:20 +0000 (UTC) Received: from mail-yi0-f53.google.com (mail-yi0-f53.google.com [209.85.218.53]) by pigeon.gentoo.org (Postfix) with ESMTP id BBAE2E0138 for ; Mon, 17 Jan 2011 19:14:20 +0000 (UTC) Received: by yib17 with SMTP id 17so2671277yib.12 for ; Mon, 17 Jan 2011 11:14:20 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=domainkey-signature:message-id:from:to:subject:date :x-kmail-transport:x-kmail-fcc:x-kmail-drafts:x-kmail-templates :x-kmail-link-message:x-kmail-link-type:user-agent:in-reply-to :references:mime-version:content-transfer-encoding:content-type; bh=Ls4GbyJiJGQttOdyri4KiPsyjgsWgcslQGZOnDRjwwM=; b=TdwyPICnjUPZvdMjL/PKK8AtvvmX2lz+4BiZTWRIMT2Hl8O+0ov3xzliv/ED2z6b9l SyakeHii3QIW9lupnXCJwbsCeFGEdJxmwWg9OEaC5krxd5Ye+/lIJFf0myfB7OpvlE7N Up+Yz7aKhs9oMc/tDCUtmqIxEIFJ3i1j7HZtE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=googlemail.com; s=gamma; h=message-id:from:to:subject:date:x-kmail-transport:x-kmail-fcc :x-kmail-drafts:x-kmail-templates:x-kmail-link-message :x-kmail-link-type:user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; b=FrtJe5lOI72Xdwy0ptgIGK29cFlvRYEOZ6ptYjyHdNPrrY8iyvcxhr1eWN+c9goeSs /mJefnrJv4aJuTH23ihjD4jj3PB4N6rG/fy74B0nThGlTfaq/lIZL0bZG9vgNJfjJn0o mECF+RTSozmolN3XS93w4oKrb9YsBgq5itkhE= Received: by 10.223.85.203 with SMTP id p11mr5120336fal.108.1295291659311; Mon, 17 Jan 2011 11:14:19 -0800 (PST) Received: from energy.localnet (p4FC74DE2.dip0.t-ipconnect.de [79.199.77.226]) by mx.google.com with ESMTPS id a2sm1805032faw.22.2011.01.17.11.14.17 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 17 Jan 2011 11:14:18 -0800 (PST) Message-ID: <4d34950a.0297df0a.5e61.ffffceff@mx.google.com> From: Volker Armin Hemmann To: gentoo-user@lists.gentoo.org Subject: Re: [gentoo-user] Microcode update AMD Date: Mon, 17 Jan 2011 20:14:16 +0100 X-KMail-Transport: googlemail X-KMail-Fcc: 32 X-KMail-Drafts: 14 X-KMail-Templates: 35 X-KMail-Link-Message: 124925 X-KMail-Link-Type: reply User-Agent: KMail/4.6 beta3 (Linux/2.6.36.3r4; KDE/4.5.95; x86_64; ; ) In-Reply-To: <20110117183408.GG5748@solfire> References: <20110117172148.GD5748@solfire> <324412.67436.qm@web39307.mail.mud.yahoo.com> <20110117183408.GG5748@solfire> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-user@lists.gentoo.org Reply-to: gentoo-user@lists.gentoo.org MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" X-Archives-Salt: 9fe286fa-6c5c-4312-862c-666d2847d18e X-Archives-Hash: 4731133672be084c5d1816c90cf547a5 On Monday 17 January 2011 19:34:08 meino.cramer@gmx.de wrote: > BRM [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.