From: Thiemo Seufer <ths@networkno.de>
To: Stuart Anderson <anderson@netsweng.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] clone syscall fix
Date: Sat, 31 Mar 2007 20:21:04 +0100 [thread overview]
Message-ID: <20070331192104.GC24690@networkno.de> (raw)
In-Reply-To: <Pine.LNX.4.64.0703292140020.514@trantor.stuart.netsweng.com>
Stuart Anderson wrote:
>
> Even though clone() and fork() are related, they don't seem to be close
> enough to allow a single routine to be used to implement both. With this
> patch, the LTP tests for clone now pass.
But it still does the same, assuming VM_CLONE is set, except for passing
additional arguments to the host call. Passing untranslated regs looks
like a bug to me, I'm unsure about the tls_val.
> It may be possible to fold this back into do_fork(), but this just seemed to
> be a little bit more straightforward.
Since Linux's fork() is just a specialcase of clone() this should be
done eventually.
Thiemo
next prev parent reply other threads:[~2007-03-31 19:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-30 1:45 [Qemu-devel] [PATCH] clone syscall fix Stuart Anderson
2007-03-31 19:21 ` Thiemo Seufer [this message]
2007-04-01 1:52 ` Stuart Anderson
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=20070331192104.GC24690@networkno.de \
--to=ths@networkno.de \
--cc=anderson@netsweng.com \
--cc=qemu-devel@nongnu.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).