From: BlaisorBlade <blaisorblade_spam@yahoo.it>
To: user-mode-linux-devel@lists.sourceforge.net
Cc: Jeff Dike <jdike@addtoit.com>, David Jeffery <djeffery@britsys.net>
Subject: Re: [uml-devel] [PATCH] nptl/sys_clone fix for i386/ppc
Date: Sat, 11 Sep 2004 17:45:18 +0200 [thread overview]
Message-ID: <200409111745.18659.blaisorblade_spam@yahoo.it> (raw)
In-Reply-To: <200409102352.i8ANql0O004842@ccure.user-mode-linux.org>
On Saturday 11 September 2004 01:52, Jeff Dike wrote:
> djeffery@britsys.net said:
> > The problem is caused by the incorrect implementation of sys_clone().
> > sys_clone() is an ugly beast that has different arguements depending
> > on the architecture. For i386 and ppc, the child tid is passed as
> > the 5th arguement instead of as the 4th arguement as as some other
> > architectures (like x86-64) do. The 4th arguement on i386 and ppc
> > doesn't look to be used by the kernel.
>
> This is fixed in my tree. It was a lot simpler than your patch, or what I
> led you to believe. I just moved sys_clone from syscall_kern.c to
> arch/um/sys-i386/syscalls.c and fixed the interface.
Jeff, please fix your patch again - the unused argument is the fourth, not the
third:
original one
+#if defined(__subarch_i386__) || defined(__subarch_ppc__)
+long sys_clone_5arg(unsigned long clone_flags, unsigned long newsp,
+ int *parent_tid, unsigned long unused, int *child_tid)
+{
+ return sys_clone(clone_flags, newsp, parent_tid, child_tid);
+}
+#endif
Also, Andrew Morton wrote some UML fixes (for scheduler bugs) on his own. Did
you already note this or you want them forwarded?
--
Paolo Giarrusso, aka Blaisorblade
Linux registered user n. 292729
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM.
Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
User-mode-linux-devel mailing list
User-mode-linux-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
next prev parent reply other threads:[~2004-09-11 15:48 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-26 2:06 [uml-devel] [PATCH] nptl/sys_clone fix for i386/ppc David Jeffery
2004-09-05 15:35 ` BlaisorBlade
2004-09-07 23:12 ` Michael Ralston
2004-09-10 23:52 ` Jeff Dike
2004-09-11 13:33 ` [uml-devel] " Sven Köhler
2004-09-11 14:18 ` Ralph Paßgang
2004-09-11 15:19 ` BlaisorBlade
2004-09-11 20:11 ` Sven Köhler
2004-09-12 18:19 ` BlaisorBlade
2004-09-11 15:45 ` BlaisorBlade [this message]
2004-09-11 18:26 ` [uml-devel] " Jeff Dike
2004-09-12 15:52 ` BlaisorBlade
2004-09-13 3:10 ` Jeff Dike
2004-09-13 18:50 ` BlaisorBlade
2004-09-12 15:54 ` [uml-devel] Unsent fixes by Andrew Morton BlaisorBlade
[not found] <BACKUPJQjdF8qoH28Db000022d5@NOSPAM.BRITSYS.NET>
2004-09-08 0:29 ` [uml-devel] [PATCH] nptl/sys_clone fix for i386/ppc David Jeffery
2004-09-08 18:09 ` BlaisorBlade
-- strict thread matches above, loose matches on Subject: below --
2004-09-11 22:27 Wichmann, Mats D
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=200409111745.18659.blaisorblade_spam@yahoo.it \
--to=blaisorblade_spam@yahoo.it \
--cc=djeffery@britsys.net \
--cc=jdike@addtoit.com \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/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