On Fri, Jun 25, 2004 at 10:56:31 +0530, sajay@temenos.com wrote: > Hi, > > I have a doubt in the Non Preemptive Kernel. In the case of a Non > Preemptive Kernel, the Kernel Control Path cannot be preempted unless it > relinquishes the CPU Voluntarily. In this scenario, supposing a Timer > interrupt occurs, how does the timer Interrupt handler find out that a > Kernel Control Path is running and hence the process shouldn't be > preempted. Or is this handled by the schedule() function. It does not. IIRC schedule happens during return to userspace. Return to userspace does not happen if the interrupt interrupted kernel code. And note, that it really happens during EACH return to userspace (if need_resched is set), so if interrupt causes process to wake up, it's scheduled soon. ------------------------------------------------------------------------------- Jan 'Bulb' Hudec <bulb@ucw.cz>
Attachment:
signature.asc
Description: Digital signature
