From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <libc-alpha-return-93215-listarch-libc-alpha=sources.redhat.com@sourceware.org>
Received: (qmail 16810 invoked by alias); 13 Jun 2018 21:45:27 -0000
Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm
Precedence: bulk
List-Id: <libc-alpha.sourceware.org>
List-Subscribe: <mailto:libc-alpha-subscribe@sourceware.org>
List-Archive: <http://sourceware.org/ml/libc-alpha/>
List-Post: <mailto:libc-alpha@sourceware.org>
List-Help: <mailto:libc-alpha-help@sourceware.org>, <http://sourceware.org/ml/#faqs>
Sender: libc-alpha-owner@sourceware.org
Received: (qmail 16607 invoked by uid 89); 13 Jun 2018 21:45:05 -0000
Authentication-Results: sourceware.org; auth=none
X-Virus-Found: No
X-Spam-SWARE-Status: No, score=-1.6 required=5.0 tests=BAYES_00,KAM_LAZY_DOMAIN_SECURITY,RCVD_IN_DNSWL_LOW autolearn=no version=3.3.2 spammy=
X-HELO: mx0a-001b2d01.pphosted.com
From: Tulio Magno Quites Machado Filho <tuliom@linux.vnet.ibm.com>
To: Stefan Liebler <stli@linux.ibm.com>, Florian Weimer <fweimer@redhat.com>,
        GNU C Library <libc-alpha@sourceware.org>
Cc: 
Subject: Re: [PATCH] Fix race in pthread_mutex_lock while promoting to PTHREAD_MUTEX_ELISION_NP [BZ #23275]
In-Reply-To: <6538b117-5f58-181c-a52c-4c668ac4deb4@linux.ibm.com>
References: <f3fc33e5-aa98-f772-a1bf-c02ddf9352c7@linux.ibm.com> <4851b1b3-2fd5-75c2-cc5e-68519e373df2@redhat.com> <6538b117-5f58-181c-a52c-4c668ac4deb4@linux.ibm.com>
User-Agent: Notmuch/0.25 (http://notmuchmail.org) Emacs/25.3.1 (x86_64-redhat-linux-gnu)
Date: Wed, 13 Jun 2018 21:45:00 -0000
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
X-TM-AS-GCONF: 00
x-cbid: 18061321-0016-0000-0000-000008F7F49A
X-IBM-SpamModules-Scores: 
X-IBM-SpamModules-Versions: BY=3.00009185; HX=3.00000241; KW=3.00000007;
 PH=3.00000004; SC=3.00000265; SDB=6.01046536; UDB=6.00535988; IPR=6.00825512;
 MB=3.00021630; MTD=3.00000008; XFM=3.00000015; UTC=2018-06-13 21:44:59
X-IBM-AV-DETECTION: SAVI=unused REMOTE=unused XFE=unused
x-cbparentid: 18061321-0017-0000-0000-00003F4572EF
Message-Id: <8736xqcqeh.fsf@linux.ibm.com>
X-Proofpoint-Virus-Version: vendor=fsecure engine=2.50.10434:,, definitions=2018-06-13_09:,,
 signatures=0
X-SW-Source: 2018-06/txt/msg00369.txt.bz2

Stefan Liebler <stli@linux.ibm.com> writes:

> On 06/13/2018 10:41 AM, Florian Weimer wrote:
>> On 06/12/2018 04:24 PM, Stefan Liebler wrote:
>>> The new testcase tst-mutex10 is triggering the race on s390x and=20
>>> intel. Presumably also on power, but I don't have access to a power=20
>>> machine with lock-elision. At least the code for power is the same as=20
>>> on the other two architectures. Can somebody test it on power?
>>=20
>> I tried the test case on a machine with:
>>=20
>> Model:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 2.0 (pvr 004d 0200)
>> Model name:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=
=C2=A0 POWER8 (raw), altivec supported
>>=20
>> AT_HWCAP:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 true_le archpmu vsx =
arch_2_06 dfp ic_snoop smt mmu fpu=20
>> altivec ppc64 ppc32
>> AT_HWCAP2:=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0=C2=A0 htm-nosc vcrypto tar isel=
 ebb dscr htm arch_2_07
>>=20
>> Presumably, that should have lock elision support?
> Unfortunately, I don't know.
> @Tulio: Can you answer this question?

Yes, this server should have lock elision.

--=20
Tulio Magno