public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
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>
Subject: Re: [PATCH] Fix race in pthread_mutex_lock while promoting to PTHREAD_MUTEX_ELISION_NP [BZ #23275]
Date: Wed, 13 Jun 2018 21:45:00 -0000	[thread overview]
Message-ID: <8736xqcqeh.fsf@linux.ibm.com> (raw)
In-Reply-To: <6538b117-5f58-181c-a52c-4c668ac4deb4@linux.ibm.com>

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 
>>> intel. Presumably also on power, but I don't have access to a power 
>>> machine with lock-elision. At least the code for power is the same as 
>>> on the other two architectures. Can somebody test it on power?
>> 
>> I tried the test case on a machine with:
>> 
>> Model:                 2.0 (pvr 004d 0200)
>> Model name:            POWER8 (raw), altivec supported
>> 
>> AT_HWCAP:        true_le archpmu vsx arch_2_06 dfp ic_snoop smt mmu fpu 
>> altivec ppc64 ppc32
>> AT_HWCAP2:       htm-nosc vcrypto tar isel ebb dscr htm arch_2_07
>> 
>> 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.

-- 
Tulio Magno

  parent reply	other threads:[~2018-06-13 21:45 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-12 14:25 Stefan Liebler
2018-06-13  8:43 ` Florian Weimer
2018-06-13  9:18   ` Stefan Liebler
2018-06-13  9:36     ` Florian Weimer
2018-06-13 15:25       ` Stefan Liebler
2018-06-14  8:04         ` Stefan Liebler
2018-06-13 21:45     ` Tulio Magno Quites Machado Filho [this message]
2018-06-19  7:45 ` Stefan Liebler
2018-06-26  6:45   ` [PING][PATCH] " Stefan Liebler
2018-07-03  6:28     ` Stefan Liebler
2018-07-10  6:34       ` Stefan Liebler
2018-07-16 11:57         ` Stefan Liebler
2018-07-23  6:42           ` Stefan Liebler
2018-07-30  7:22             ` Stefan Liebler
2018-08-27  9:12               ` Stefan Liebler
2018-09-03  7:10                 ` Stefan Liebler
2018-09-10 12:01                   ` Stefan Liebler
2018-09-17 13:38 ` [PATCH] " Florian Weimer
2018-10-04 16:08   ` Stefan Liebler
2018-10-16 14:23     ` Florian Weimer
2018-10-17 10:36       ` Stefan Liebler
2018-10-18 13:24         ` [COMMITTED 2.27 / 2.28] " Stefan Liebler

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=8736xqcqeh.fsf@linux.ibm.com \
    --to=tuliom@linux.vnet.ibm.com \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=stli@linux.ibm.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).