linux-kernel - Re: microcode loading got really slow.

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] [day] [month] [year] [list]

Date:	Thu, 23 May 2013 11:55:32 -0400
From:	Dave Jones <davej@...hat.com>
To:	Ming Lei <tom.leiming@...il.com>
Cc:	Takashi Iwai <tiwai@...e.de>, "H. Peter Anvin" <hpa@...or.com>,
	Linux Kernel <linux-kernel@...r.kernel.org>, x86@...nel.org,
	fenghua.yu@...el.com
Subject: Re: microcode loading got really slow.

On Thu, May 23, 2013 at 11:27:08PM +0800, Ming Lei wrote:
 > > Yes, in your case, everything is fine in the kernel itself.  And no
 > > microcode update is needed for new CPU, thus no firmware.
 > 
 > Can the driver decide if the CPU need microcode? Or there will
 > be the microcode for the CPU in future?

The kernel can't know. The microcode updates are asynchonously released
from the kernel. I might be running a months old kernel, and get a new
microcode tomorrow.  The kernel handles this by looking for a file
with a name matching the cpu family/model/stepping. (See how they are
formed in /lib/firmware/intel-ucode/*)

	DAve

--
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/