From: Steven Munroe <munroesj@us.ibm.com>
To: Jakub Jelinek <jakub@redhat.com>
Cc: Ulrich Drepper <drepper@redhat.com>,
GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: Re: [PATCH] clean up PPC for private futex changes.
Date: Mon, 23 Jul 2007 22:09:00 -0000 [thread overview]
Message-ID: <46A52700.50905@us.ibm.com> (raw)
In-Reply-To: <20070723204237.GE4603@sunsite.mff.cuni.cz>
Jakub Jelinek wrote:
>On Mon, Jul 23, 2007 at 09:10:27AM -0700, Ulrich Drepper wrote:
>
>
>>-----BEGIN PGP SIGNED MESSAGE-----
>>Hash: SHA1
>>
>>Applied.
>>
>>
>
>Unfortunately that patch contains several important bugs:
>1) lll_futex_wait etc. had only correct definition when
> __ASSUME_PRIVATE_FUTEX, when that is not true, it would
> call futex syscall with bit 7 set even when libpthread.so
> init determined it is not supported
>
>
Ya, I was looking at the x86_64 code which did seem incomplete to me. So
I tried to go one step better for PPC.
But how can header.private_futex be set in the absence of
__ASSUME_PRIVATE_FUTEX?
>2) lll_private_futex_wait etc. macros were shared when
> not __ASSUME_PRIVATE_FUTEX
>3) FUTEX_WAKE_OP had the wake operation argument also ored
> with 128 in some cases
>
>
Ya, I was concerned about that, but the examples from i386 and x86_64
where not clear to me...
>Here is how it IMHO should look like (built and tested on ppc64-linux,
>unfortunately not wiht a 2.6.23ish kernel).
>
>
This looks better. Thanks
next prev parent reply other threads:[~2007-07-23 22:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-13 20:44 Steven Munroe
2007-07-23 16:10 ` Ulrich Drepper
2007-07-23 20:43 ` Jakub Jelinek
2007-07-23 22:09 ` Steven Munroe [this message]
2007-07-24 7:11 ` Jakub Jelinek
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=46A52700.50905@us.ibm.com \
--to=munroesj@us.ibm.com \
--cc=drepper@redhat.com \
--cc=jakub@redhat.com \
--cc=libc-hacker@sources.redhat.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).