[PATCH] 2.5.68 FUTEX support should be optional

Christopher Hoover (ch@murgatroid.com)
Tue, 13 May 2003 21:32:07 -0700


Not everyone needs futex support, so it should be optional. This is
needed for small platforms.

-ch
mailto:ch(at)murgatroid.com
mailto:ch(at)hpl.hp.com

diff -X dontdiff.txt -Naurp linux-2.5.68-rmk1/kernel/Makefile linux-2.5.68-rmk1-ceiva1/kernel/Makefile
--- linux-2.5.68-rmk1/kernel/Makefile 2003-04-19 19:48:55.000000000 -0700
+++ linux-2.5.68-rmk1-ceiva1/kernel/Makefile 2003-05-13 20:58:54.000000000 -0700
@@ -5,9 +5,10 @@
obj-y = sched.o fork.o exec_domain.o panic.o printk.o profile.o \
exit.o itimer.o time.o softirq.o resource.o \
sysctl.o capability.o ptrace.o timer.o user.o \
- signal.o sys.o kmod.o workqueue.o futex.o pid.o \
+ signal.o sys.o kmod.o workqueue.o pid.o \
rcupdate.o intermodule.o extable.o params.o posix-timers.o

+obj-$(CONFIG_FUTEXT) += futex.o
obj-$(CONFIG_GENERIC_ISA_DMA) += dma.o
obj-$(CONFIG_SMP) += cpu.o
obj-$(CONFIG_UID16) += uid16.o
diff -X dontdiff.txt -Naurp linux-2.5.68-rmk1/kernel/sys.c linux-2.5.68-rmk1-ceiva1/kernel/sys.c
--- linux-2.5.68-rmk1/kernel/sys.c 2003-04-19 19:48:51.000000000 -0700
+++ linux-2.5.68-rmk1-ceiva1/kernel/sys.c 2003-05-13 21:06:02.000000000 -0700
@@ -226,6 +226,7 @@ cond_syscall(sys_shutdown)
cond_syscall(sys_sendmsg)
cond_syscall(sys_recvmsg)
cond_syscall(sys_socketcall)
+cond_syscall(sys_futex)

static int set_one_prio(struct task_struct *p, int niceval, int error)
{
diff -X dontdiff.txt -Naurp linux-2.5.68-rmk1/init/Kconfig linux-2.5.68-rmk1-ceiva1/init/Kconfig
--- linux-2.5.68-rmk1/init/Kconfig 2003-04-19 19:50:38.000000000 -0700
+++ linux-2.5.68-rmk1-ceiva1/init/Kconfig 2003-05-13 21:25:39.000000000 -0700
@@ -108,8 +108,14 @@ config LOG_BUF_SHIFT
13 => 8 KB
12 => 4 KB

-endmenu

+config FUTEX
+ bool "Futex support"
+ default y
+ ---help---
+ Say Y if you want support for Fast Userspace Mutexes (Futexes).
+
+endmenu

menu "Loadable module support"

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