Date: Tue, 3 Nov 1998 09:23:18 -0500 (EST) From: Brian Feldman <green@zone.syracuse.net> To: Luoqi Chen <luoqi@watermarkgroup.com> Cc: dot@dotat.at, current@FreeBSD.ORG Subject: Re: Linux clone() Message-ID: <Pine.BSF.4.05.9811030921570.27548-100000@zone.syracuse.net> In-Reply-To: <199811030359.WAA24618@lor.watermarkgroup.com>
next in thread | previous in thread | raw e-mail | index | archive | help
I'll be able to handle all this, don't worry :) Right now I'm just
figureing out how to pop the stuff off, if I should... I'll know in a few
ins.
Brian Feldman
On Mon, 2 Nov 1998, Luoqi Chen wrote:
> > > Hmmm.. okay this would be a good test. Right now I'm going thru the
> > > various linuxthreads example programs.... The patch seems to be doing
> > > something wrong, and I'm unable to figure out what to do, due to Linux's
> > > humongously gross syscall system (so the kernel doesn't help me). It also
> > > seems now I was implementing a LIBRARY function, which is just a wrapper.
> > > If I could get my hands on what the real system calls' args are it would
> > > be great.
> > >
> > > Brian Feldman
> > >
> > It seems that clone() the syscall takes two arguments:
> > struct linux_clone_args {
> > int flags;
> > void *stack;
> > };
> > the wrapper in library takes care of pushing the function address and its
> > argument on to the stack. You probably also want to map linux clone flags
> > to that of rfork's: CLONE_FILES -> RFFDG, CLONE_VM -> RFMEM.
> I made a mistake, it should be !CLONE_FILES -> RFFDG. And there's no rfork()
> counterpart for CLONE_SIGHAND, default rfork behavior corresponds to
> !CLONE_SIGHAND.
>
> -lq
>
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.05.9811030921570.27548-100000>