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]

Date:	Thu, 12 Mar 2009 07:07:59 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	"Giacomo A. Catenazzi" <cate@...eee.net>
Cc:	Sitsofe Wheeler <sitsofe@...oo.com>,
	Dragoslav Zaric <dragoslav.zaric.kd@...il.com>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: Linux* Processor Microcode Data File

On Thu, 12 Mar 2009 11:03:11 +0100
"Giacomo A. Catenazzi" <cate@...eee.net> wrote:

> > 
> > there are various cases where microcode is needed (for example, when
> > you hotplug a new cpu); request_firmware() is just the right way to
> > do such things, and an initscript is just the wrong way
> 
> I don't agree ;-)
> I agree that request_firmware method is better than init.d scripts,
> but not that it is the right things. microcodes should be loaded at
> very beginning of boot process, so by BIOS, by GRUB or on hotpug
> event by request_firmware.

... and how do you do CPU hotplug then ?

> BTW: why do we have microcode loading modular?

only the legacy initscript part is modular afaik.



-- 
Arjan van de Ven 	Intel Open Source Technology Centre
For development, discussion and tips for power savings, 
visit http://www.lesswatts.org
--
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/