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 for Android: free password hash cracker in your pocket

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

Message-ID: <20080920061145.GD25713@elte.hu>
Date:	Sat, 20 Sep 2008 08:11:45 +0200
From:	Ingo Molnar <mingo@...e.hu>
To:	"Giacomo A. Catenazzi" <cate@...ian.org>
Cc:	Peter Oruba <peter.oruba@....com>,
	Dmitry Adamushko <dmitry.adamushko@...il.com>,
	Arjan van de Ven <arjan@...radead.org>,
	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.

* Giacomo A. Catenazzi <cate@...ian.org> wrote:

>> That sounds like a single-module solution would be the best way to 
>> go. All dependencies would then be handled inside the module.
>
> Single module probably is more difficult to maintain.

why? In this case we have just two relevant CPU microcode drivers - and 
we dont expect their number to grow significantly. So it should be 
perfectly clean to link everything into a single module.

In fact as this example has shown it a single-module solution has 
numerous advantages, as it simplifies userspace interactions.

Taken to the extreme, a single-image (bzImage) kernel has many 
advantages over a many-modules kernel as well. So we only want to 
modularize when we absolutely have to, and this is not one of those 
cases.

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