linux-kernel - Re: [patch 05/11] [PATCH 05/11] x86: Moved microcode.c to microcode

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: <48CA745B.2070605@debian.org>
Date:	Fri, 12 Sep 2008 15:53:31 +0200
From:	"Giacomo A. Catenazzi" <cate@...ian.org>
To:	Arjan van de Ven <arjan@...radead.org>
CC:	Peter Oruba <peter.oruba@....com>, Ingo Molnar <mingo@...e.hu>,
	Thomas Gleixner <tglx@...utronix.de>,
	Tigran Aivazian <tigran@...azian.fsnet.co.uk>,
	LKML <linux-kernel@...r.kernel.org>
Subject: Re: [patch 05/11] [PATCH 05/11] x86: Moved microcode.c to microcode_intel.c.

Arjan van de Ven wrote:
> On Fri, 12 Sep 2008 13:54:20 +0200
> Peter Oruba <peter.oruba@....com> wrote:
> 
>> Arjan,
>>
>> could you please provide some more information about that issue?
> 
> well.. the fedora boot script just plain fails.
> I suspect it manually loads microcode.ko or something if CPUID says
> intel; and this now stops working...

Also Debian manually load the module, and it remove it
after upgrading microcode (no need to have the
driver loaded after boot), so changing the name of
module is not so fortunate, also considering the
long releases cycle of Debian.

I would like to have a single microcode module for the
two drivers: generic kernel need both (thus reduce
overhead); specialized kernel are configured only with
the relevant driver, so no additional overhead.

ciao
	cate

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