Re: Question on Schedule and Preemption

[Arjan van de Ven]

> If the current task is running and thus not yet exiting (!current->exit_state)
> and is also in an atomic code section (i.e. under lock), it shouldn't call
> any reschedule function (which also happens by just calling msleep(): use
> mdelay() instead in that case!).
> 

actually don't use mdelay, but change your code so that you CAN sleep :)


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/