From: Ralf Baechle <ralf@oss.sgi.com>
To: kjlin <kj.lin@viditec-netmedia.com.tw>
Cc: linux-mips@oss.sgi.com
Subject: Re: fork() vs vfork()
Date: Thu, 20 Sep 2001 13:29:35 +0200 [thread overview]
Message-ID: <20010920132935.A13439@dea.linux-mips.net> (raw)
In-Reply-To: <05e901c141a0$a03e6120$056aaac0@kjlin>; from kj.lin@viditec-netmedia.com.tw on Thu, Sep 20, 2001 at 02:51:08PM +0800
On Thu, Sep 20, 2001 at 02:51:08PM +0800, kjlin wrote:
> From: "kjlin" <kj.lin@viditec-netmedia.com.tw>
> To: <linux-mips@oss.sgi.com>
> Subject: fork() vs vfork()
> Date: Thu, 20 Sep 2001 14:51:08 +0800
>
> Hi all,
>
> How does linux-mips treat the vfork() function?
> I can see the fork() implemented in syscall.c as following:
>
> save_static_function(sys_fork);
> static_unused int _sys_fork(struct pt_regs regs)
> {
> int res;
> res = do_fork(SIGCHLD, regs.regs[29], ®s, 0);
> return res;
> }
> Why not do the same "sys_vfork" in linux-mips?
> Does it mean that MIPS does not support vfork() or vfork() is equal to fork() in MIPS platform?
Hint: save_static_function is a macro.
Ralf
prev parent reply other threads:[~2001-09-20 11:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-09-20 6:51 fork() vs vfork() kjlin
2001-09-20 6:51 ` kjlin
2001-09-20 11:29 ` Ralf Baechle [this message]
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=20010920132935.A13439@dea.linux-mips.net \
--to=ralf@oss.sgi.com \
--cc=kj.lin@viditec-netmedia.com.tw \
--cc=linux-mips@oss.sgi.com \
/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.