All of lore.kernel.org
 help / color / mirror / Atom feed
From: Nathan Straz <nstraz@sgi.com>
To: linux-ia64@vger.kernel.org
Subject: Re: clone testcases in LTP
Date: Thu, 10 Jul 2003 16:18:38 +0000	[thread overview]
Message-ID: <marc-linux-ia64-105785417917339@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-105778639326638@msgid-missing>

On Wed, Jul 09, 2003 at 03:17:42PM -0700, David Mosberger wrote:
> The only difference between clone() and clone2() is the explicit
> stack-size argument.  clone2() is discussed in detail in my book, but
> if you're already familiar with clone(), it's easy to understand
> what's going on.  Here is the pseudo prototype (from glibc):
> 
> /* int  __clone2(int (*fn) (void *arg), void *child_stack_base,	*/
> /*	         size_t child_stack_size, int flags, void *arg,		*/
> /*	         pid_t *parent_tid, void *tls, pid_t *child_tid)	*/

Hmm, that prototype seems to have a lot more args than the clone man
page states:

   #include <sched.h>
   int clone(int (*fn)(void *), void *child_stack, int flags, void *arg);
   _syscall2(int, clone, int, flags, void *, child_stack);

What are the parameters parent_tid, tls, and child_tid supposed to be?
-- 
Nate Straz                                              nstraz@sgi.com
sgi, inc                                           http://www.sgi.com/
Linux Test Project                                  http://ltp.sf.net/

  parent reply	other threads:[~2003-07-10 16:18 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-07-09 21:32 clone testcases in LTP Nathan Straz
2003-07-09 22:17 ` David Mosberger
2003-07-10 16:18 ` Nathan Straz [this message]
2003-07-10 16:25 ` David Mosberger
2003-07-10 23:22 ` Peter Chubb
2003-07-10 23:31 ` David Mosberger
2003-07-11  0:04 ` Peter Chubb
2003-07-11  0:35 ` Ian Wienand
2003-07-11  0:44 ` David Mosberger
2003-07-11  9:57 ` Andreas Schwab
2003-07-11 14:15 ` Nathan Straz
2003-07-11 18:49 ` Andreas Schwab

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-linux-ia64-105785417917339@msgid-missing \
    --to=nstraz@sgi.com \
    --cc=linux-ia64@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.