From: george anzinger <george@mvista.com>
To: Russell King <rmk@arm.linux.org.uk>
Cc: "Victor Yodaiken" <yodaiken@fsmlabs.com>,
"christophe barbé" <christophe.barbe@lineo.fr>,
linux-kernel@vger.kernel.org
Subject: Re: How should nano_sleep be fixed (was: ptrace(), fork(), sleep(), exit(), SIGCHLD)
Date: Thu, 23 Aug 2001 13:04:09 -0700 [thread overview]
Message-ID: <3B8561B9.AC440835@mvista.com> (raw)
In-Reply-To: <20010817125727.A16475@hq2> <3B7D76EF.DA34EB23@mvista.com> <20010822194035.K18391@flint.arm.linux.org.uk>
Russell King wrote:
>
> On Fri, Aug 17, 2001 at 12:56:31PM -0700, george anzinger wrote:
> > Uh..? I though that was what I was allowing. It seems to me to be a
> > lot of extra work to put the same code in 15 different archs.
> > Especially if one does not really know each of them, nor can any one
> > group (or individual) be expected to be able to test (or even have the
> > hardware to test) each of them.
>
> Umm, my best advice is to look at sys_fork() and do_fork(), sys_execve()
> and do_execve().
>
Sorry, but none of those system calls requires the registers which is
where the problem is.
George
next prev parent reply other threads:[~2001-08-23 20:04 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-13 8:29 ptrace(), fork(), sleep(), exit(), SIGCHLD Bruce Janson
2001-08-14 7:28 ` christophe barbé
2001-08-14 15:06 ` Bruce Janson
2001-08-15 15:46 ` george anzinger
2001-08-15 17:53 ` george anzinger
2001-08-15 18:02 ` george anzinger
2001-08-16 0:59 ` How should nano_sleep be fixed (was: ptrace(), fork(), sleep(), exit(), SIGCHLD) george anzinger
2001-08-16 10:17 ` christophe barbé
2001-08-16 10:29 ` Russell King
2001-08-16 14:16 ` george anzinger
2001-08-16 16:00 ` christophe barbé
2001-08-16 16:12 ` Russell King
2001-08-16 18:17 ` george anzinger
2001-08-17 18:25 ` george anzinger
2001-08-17 18:57 ` Victor Yodaiken
2001-08-17 19:56 ` george anzinger
2001-08-22 18:40 ` Russell King
2001-08-23 20:04 ` george anzinger [this message]
2001-08-23 20:11 ` Russell King
2001-08-23 21:13 ` george anzinger
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=3B8561B9.AC440835@mvista.com \
--to=george@mvista.com \
--cc=christophe.barbe@lineo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=rmk@arm.linux.org.uk \
--cc=yodaiken@fsmlabs.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.