Skip to contentSkip to conversation

i386: let REGPARM no longer depend on EXPERIMENTAL

PATCH In review Adrian Bunk 2 participants 2 messages Jan 6, 2006

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 i386: let REGPARM no longer depend on EXPERIMENTAL

REGPARM has already gotten much testing, what about removing the dependency on EXPERIMENTAL?

Additionally, this patch does:
- remove the useless "default n"
- remove note regarding binary only modules (nowadays, there are even some binary only modules compiled with REGPARM=y available)

arch/i386/Kconfig renamed from arch/i386/Kconfig.old +1 -4
@@ -626,13 +626,10 @@
 	default y
 
 config REGPARM
-	bool "Use register arguments (EXPERIMENTAL)"
-	depends on EXPERIMENTAL
-	default n
+	bool "Use register arguments"
 	help
 	Compile the kernel with -mregparm=3. This uses a different ABI
 	and passes the first three arguments of a function call in registers.
-	This will probably break binary only modules.
 
 config SECCOMP
 	bool "Enable seccomp to safely compute untrusted bytecode"
#1 lore raw
Quoted 3 lines

REGPARM has already gotten much testing, what about removing the dependency on EXPERIMENTAL?

I had no problem with it since I started using it from 2.6.8 on. (Some machines starting with 2.6.11 because I forgot to activate it in menuconfig.)

Quoted 4 lines

Additionally, this patch does:
- remove the useless "default n"
- remove note regarding binary only modules (nowadays, there are even some binary only modules compiled with REGPARM=y available)

Prop nvidia module (1.0-4496 tho) works with REGPARM=y.

Jan Engelhardt

Signature · 2 lines
| Alphagate Systems, http://alphagate.hopto.org/
| jengelh's site, http://jengelh.hopto.org/