From mboxrd@z Thu Jan 1 00:00:00 1970 Received: (from majordomo@localhost) by oss.sgi.com (8.11.2/8.11.3) id f8K7Box14917 for linux-mips-outgoing; Thu, 20 Sep 2001 00:11:50 -0700 Received: from viditec-netmedia.com.tw (61-220-240-70.HINET-IP.hinet.net [61.220.240.70]) by oss.sgi.com (8.11.2/8.11.3) with SMTP id f8K7BQe14906 for ; Thu, 20 Sep 2001 00:11:28 -0700 Received: from kjlin ([61.220.240.66]) by viditec-netmedia.com.tw (8.10.0/8.10.0) with SMTP id f8K9nUI04761 for ; Thu, 20 Sep 2001 17:49:30 +0800 Message-ID: <05e901c141a0$a03e6120$056aaac0@kjlin> From: "kjlin" To: Subject: fork() vs vfork() Date: Thu, 20 Sep 2001 14:51:08 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_05E6_01C141E3.AE47B080" X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 5.00.2919.6600 X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2919.6600 Sender: owner-linux-mips@oss.sgi.com Precedence: bulk This is a multi-part message in MIME format. ------=_NextPart_000_05E6_01C141E3.AE47B080 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: quoted-printable 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 =3D do_fork(SIGCHLD, regs.regs[29], ®s, 0); return res; } But i can't see anything about vfork/sys_vfork in mips platform. However, the vfork() was implemented as sys_vfork in other architecture. Such as arm platform: asmlinkage int sys_vfork(struct pt_regs *regs) { return do_fork(CLONE_VFORK | CLONE_VM | SIGCHLD, regs->ARM_sp, = regs, 0); } 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? Thanks, KJ ------=_NextPart_000_05E6_01C141E3.AE47B080 Content-Type: text/html; charset="big5" Content-Transfer-Encoding: quoted-printable

Hi all,

How does linux-mips treat the vfork() = function?

I can see the fork() implemented in syscall.c as=20 following:

save_static_function(sys_fork);
static_unused int = _sys_fork(struct pt_regs=20 regs)
{
int = res;

res =3D=20 do_fork(SIGCHLD, regs.regs[29], &regs, 0);

return=20 res;
}

But i can't see anything about = vfork/sys_vfork in=20 mips platform.

However, the vfork() was implemented as sys_vfork in = other=20 architecture.

Such as arm platform:

asmlinkage int sys_vfork(struct pt_regs=20 *regs)
{
return=20 do_fork(CLONE_VFORK | CLONE_VM | SIGCHLD, regs->ARM_sp, regs,=20 0);
}

Why not do the same "sys_vfork" in = linux-mips?

Does it mean that MIPS does not support vfork() or = vfork() is=20 equal to fork() in MIPS platform?

Thanks,

------=_NextPart_000_05E6_01C141E3.AE47B080-- From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <05e901c141a0$a03e6120$056aaac0@kjlin> From: "kjlin" Subject: fork() vs vfork() Date: Thu, 20 Sep 2001 14:51:08 +0800 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_NextPart_000_05E6_01C141E3.AE47B080" Sender: owner-linux-mips@oss.sgi.com To: linux-mips@oss.sgi.com Message-ID: <20010920065108.7UDBjRtZMDHzkQva_pn4o-UOafe78lgaLuxMnRd8X1c@z> This is a multi-part message in MIME format. ------=_NextPart_000_05E6_01C141E3.AE47B080 Content-Type: text/plain; charset="big5" Content-Transfer-Encoding: quoted-printable 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 =3D do_fork(SIGCHLD, regs.regs[29], ®s, 0); return res; } But i can't see anything about vfork/sys_vfork in mips platform. However, the vfork() was implemented as sys_vfork in other architecture. Such as arm platform: asmlinkage int sys_vfork(struct pt_regs *regs) { return do_fork(CLONE_VFORK | CLONE_VM | SIGCHLD, regs->ARM_sp, = regs, 0); } 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? Thanks, KJ ------=_NextPart_000_05E6_01C141E3.AE47B080 Content-Type: text/html; charset="big5" Content-Transfer-Encoding: quoted-printable