From: Steve Munroe <sjmunroe@us.ibm.com>
To: Thorsten Kukuk <kukuk@suse.de>
Cc: libc-hacker@sources.redhat.com
Subject: Re: lll_lock on PPC
Date: Tue, 22 Jun 2004 21:13:00 -0000 [thread overview]
Message-ID: <OF486FC584.32BF2CB3-ON86256EBB.0073D9EF-86256EBB.007492A3@us.ibm.com> (raw)
In-Reply-To: <20040622193504.GA24299@suse.de>
Thorsten Kukuk <kukuk@suse.de> wrote on 06/22/2004 02:35:04 PM:
>
> Hi,
>
> if I look at the lll_lock implementation on ix86 and PPC, it seems
> to me, that on ix86, lll_lock will only call lll_mutex_lock, if
> the program is linked against libpthread. But on PPC, lll_lock is
> always called, which can lead to a deadlock.
>
> Is this correct?
For POWER lll_mutex_lock is a inline macro using
atomic_compare_and_exchange_val_acq. lll_lock is just an alias for
lll_mutex_lock:
#define lll_lock(lock) lll_mutex_lock (lock)
There is no call. See
libc/nptl/sysdeps/unix/sysv/linux/powerpc/lowlevellock.h
Steven J. Munroe
Linux on Power Toolchain Architect
IBM Corporation, Linux Technology Center
prev parent reply other threads:[~2004-06-22 21:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-22 19:36 Thorsten Kukuk
2004-06-22 21:13 ` Steve Munroe [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=OF486FC584.32BF2CB3-ON86256EBB.0073D9EF-86256EBB.007492A3@us.ibm.com \
--to=sjmunroe@us.ibm.com \
--cc=kukuk@suse.de \
--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).