Prev: cfq-iosched: Add additional blktrace log messages in CFQ for easier debugging.
Next: DMAENGINE: generic channel status
From: kartikeyan sadasivuni on 25 Mar 2010 11:00
Hi,

I have a system where bootloader supports
core0 running linux (control plane).
core1 running application without OS (a data plane app).

(core0 and core1 share some physical memory)

Because of this setup and application requirements
I want to ocassionally disable preemption of linux kernel
for very small periods from user space process.


Is the following valid solution to achive this ?

I will load a kernel module foo.ko which supports the following
ioctl's from user space.


PREEMPT_DISABLE:
calls preempt_disable() from the driver (foo.ko)

PREEMPT_ENABLE:
calls premept_enable() from the driver (foo.ko)

user space process does

ioctl(FOO_FD, PREEMPT_DISABLE, ..);
do some short critcal work
ioctl(FOO_FD, PREEMPT_ENABLE, ..);


Basically I want to know, if preempt_disable() and preempt_enable()
are legal across user to kernel space swtiches are only within kernel.

I don't mind if the solution is wierd/stupid
but works on all 2.6.* kernels.

--
S.Kartikeyan
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo(a)vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
 | 
Pages: 1
Prev: cfq-iosched: Add additional blktrace log messages in CFQ for easier debugging.
Next: DMAENGINE: generic channel status