linux-kernel - Re: Linux* Processor Microcode Data File

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20090309141655.GA24213@silver.sucs.org>
Date:	Mon, 9 Mar 2009 14:16:55 +0000
From:	Sitsofe Wheeler <sitsofe@...oo.com>
To:	Dragoslav Zaric <dragoslav.zaric.kd@...il.com>
Cc:	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Linux* Processor Microcode Data File

On Mon, Mar 09, 2009 at 10:43:57AM +0100, Dragoslav Zaric wrote:

> So, does new kernel versions just copy this microcode update file in
> /etc/firmware folder or new
> instructions are replaced in assembly code ?

The kernel doesn't load microcode automatically but it can provide a
device to allow userspace to trigger a microcode update (via
/dev/cpu/microcode ). On boot the patching process is normally started
by an initscript. See http://www.urbanmyth.org/microcode/ for details.

-- 
Sitsofe | http://sucs.org/~sits/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/