current generaly has to mean current for the syscall to work. For some
syscalls it does not actually matter which process executes them. You
will have to run some in another thread than your main (because they
would block). The few processes that do care in which process they run,
you probably need to emulate them, but IIRC there is not many of them.
Note: there is implementation of this. It's called Mosix. You could look
how it does this.
> Prasad.
>
> On Thu, 20 Feb 2003, Andrea Arcangeli wrote:
> > >
> > > He is talking about directly calling the function behind the syscall,
> > > not actually executing a syscall itself.
> >
> > this is not what I understood from your previous discussion also given
> > you suggest not to do that when he can call sys_read/sys_write instead
> > because they're just exported etc.. I just wanted to add a better
> > "never".
> >
> > > syscalls should be made from userspace, not the kernel.
> >
> > This is what I tried to say.
> >
> > Andrea
> >
>
> --
> Failure is not an option
>
>
> -
> 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/
-------------------------------------------------------------------------------
Jan 'Bulb' Hudec <bulb@ucw.cz>
-
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/