![]() | |||||||||||||
Messages in this thread |
I foolishly muttered: > What if the SCHED_IDLE behaviour only applies when the process > is in userspace? Couldn't scheduler compare the process's > instruction pointer against the kernel/user break point, and > if the process is in the kernel, then just treat it like a > normal process? ...eek. I clearly wasn't thinking straight with that one. There isn't a (non-disgusting) way of determining in the scheduler if a process is executing a syscall apart from sys_sched_yield, is there. Carry on... - Kevin. - 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/ | ||||||||||||
| Last update: 2005-03-22 12:12 [from the cache] ©2003-2008 | |||||||||||||