Messages in this thread | | | Date | Sat, 20 Sep 2008 08:11:45 +0200 | From | Ingo Molnar <> | Subject | Re: [patch 05/11] [PATCH 05/11] x86: Moved microcode.c to microcode_intel.c. |
| |
* Giacomo A. Catenazzi <cate@debian.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
| |