![]() | |||||||||||||
Messages in this thread |
On Wed, 4 Dec 2002, george anzinger wrote: > > Once it changes the system call (eax, right), could the new > call code then just get the parms from the restart_block. Agreed. > I think it would be best to keep this as generic as > possible, i.e. let the new call code fetch its own> paramerers from the restart_block. We could even have one _single_ a generic "restart" system call, and have the function pointer for that be in the restart block. > My question is who sets up these values? I think you are > saying it should be the system call. Is this right? Whatever system call that return -ERESTART_RESTARTBLOCK, yes. So it would never get set up at all in the fast path. Only in the error case path of a system call that wants to have restarting capabilities. Linus - 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:31 [from the cache] ©2003-2008 | |||||||||||||