From: Ulrich Drepper <drepper@redhat.com>
To: Andi Kleen <ak@suse.de>
Cc: Linus Torvalds <torvalds@transmeta.com>,
Linux Kernel <linux-kernel@vger.kernel.org>
Subject: Re: Hammer thread fixes
Date: Sat, 15 Mar 2003 14:25:00 -0800 [thread overview]
Message-ID: <3E73A83C.2070000@redhat.com> (raw)
In-Reply-To: <20030315212438.GA8113@wotan.suse.de>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Andi Kleen wrote:
> It's incorrect like I told you last time. arg 4 is in r10. Linus please don't
> apply.
Of course is arg 4 in r10.
> The clone prototype is
>
> int clone(int flags, unsigned long newsp, void *parent_tid, void *child_tid) ;
That's the prototype in process.c. From the user level it is
int clone(int flags, unsigned long newsp, void *parent_tid, void
*child_tid, void *tlsaddr)
>
> rax: __NR_clone
> rdi: flags
> rsi: newsp
> rdx: parent_tid
> r10: child_tid
You don't get it. The parameter which is passed on is the TLS address
which does not appear in the parameter list but is passed in the *fifth*
parameter. TLS address != child_tid! The patch is correct and
regardless of what ak said, please apply it. Unlike ak's claims it is
actually tested. I'm running such a kernel and threads actually work
(unlike with the original kernel).
- --
- --------------. ,-. 444 Castro Street
Ulrich Drepper \ ,-----------------' \ Mountain View, CA 94041 USA
Red Hat `--' drepper at redhat.com `---------------------------
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
iD8DBQE+c6g82ijCOnn/RHQRApE+AJ9Aus8jJBg81L2A12ghG89HmfPz1wCgyldz
NUazXDCnqkvJ3qWAGkNbY9U=
=u/Oe
-----END PGP SIGNATURE-----
prev parent reply other threads:[~2003-03-15 22:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-15 21:03 Hammer thread fixes Ulrich Drepper
2003-03-15 21:24 ` Andi Kleen
2003-03-15 22:25 ` Ulrich Drepper [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=3E73A83C.2070000@redhat.com \
--to=drepper@redhat.com \
--cc=ak@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=torvalds@transmeta.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.