Hi... > $ cat /proc/config.gz |gunzip -c|grep PREEMPT > # CONFIG_PREEMPT_NONE is not set > # CONFIG_PREEMPT_VOLUNTARY is not set > CONFIG_PREEMPT=y > CONFIG_PREEMPT_BKL=y > CONFIG_DEBUG_PREEMPT=y > and version 2.6.15.6. > PS: Same effect in a write() syscall. Hm, I don't have 2.6.15.6 in hand, so I just use 2.6.14 as reference. I try to sneak into sys_init_module() in kernel/module.c and luckily I didn't see any preemption disable during module loading. So this must be something else. BTW, I am just thinking, does it make any difference if you add "return 0" at the end of preempt_test_init()? regards Mulyadi -- Kernelnewbies: Help each other learn about the Linux kernel. Archive: http://mail.nl.linux.org/kernelnewbies/ FAQ: http://kernelnewbies.org/faq/
