Messages in this thread |  | | From | Keith Owens <> | Subject | Re: Using %cr2 to reference "current" | Date | Mon, 12 Nov 2001 00:06:57 +1100 |
| |
On Sun, 11 Nov 2001 14:16:36 +0100, Martin Dalecki <dalecki@evision-ventures.com> wrote: >I have now a nice kernel at home, compiled with -mredparm=3 up >... Patch will follow on monday
Compiling the kernel with mregparm is going to play havoc with binary only modules (BOMs), interface mismatches all over the place. I know we do not support BOMs but there is a big difference between not supporting them and having them actively destroy the kernel because of different calling sequences.
A new feature of kbuild 2.5 is defining which CONFIG options are critical, any change to any critical config option forces a complete kernel rebuild. Modutils 2.5 will also refuse to load a module if its critical config options are different from the kernel. The current list of critical options is
CONFIG_SMP UP modules in SMP kernel or vice versa just go splat. This replaces the modversions '_smp' prefix.
CONFIG_KBUILD_GCC_VERSION Inserting a module compiled with gcc 3.0.1 into a kernel compiled with gcc 3.0.2 is a receipe for disaster. Kernel and module must be built with the same compiler.
Any changes that affect the ABI for modules must be handled via config options and those options must be on the critical list in 2.5.
Please add CONFIG_MREGPARM with a huge warning that, until kbuild 2.5 and modutils 2.5 are available, inserting a BOM is likely to destroy a kernel compiled with CONFIG_MREGPARM.
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
|  |