From: Stefan Liebler <stli@linux.vnet.ibm.com>
To: libc-alpha@sourceware.org
Cc: Martin Galvan <martin.galvan@tallertechnologies.com>,
Andi Kleen <ak@linux.intel.com>,
Adhemerval Zanella <adhemerval.zanella@linaro.org>,
tuliom@linux.vnet.ibm.com, raji@linux.vnet.ibm.com
Subject: Re: Questions about failing testcase nptl/test-mutex-printers
Date: Wed, 18 Apr 2018 06:26:00 -0000 [thread overview]
Message-ID: <c99f80dc-aa0d-30a2-0f8f-8e2f9b5763c7@linux.vnet.ibm.com> (raw)
In-Reply-To: <eb0d29f8-6048-58a8-28d3-55c3502ea82a@linux.vnet.ibm.com>
On 04/12/2018 03:54 PM, Stefan Liebler wrote:
> On 04/05/2018 08:43 AM, Stefan Liebler wrote:
>> On 03/28/2018 03:15 PM, Carlos O'Donell wrote:
>>> On 03/28/2018 06:58 AM, Stefan Liebler wrote:
>>>> Does it make sense to disable lock-elision for the
>>>> pretty-printer-tests?
>>>
>>> Yes it does, and that is probably the correct answer in this case.
>>>
>>> Many of the tests rely on looking at the internal details of the lock,
>>> particularly if you're going to pretty-print it, and elision does not
>>> allow
>>> that to happen because the lock and any modifications are elided.
>>>
>>>> E.g. with the following patch:
>>>> diff --git a/scripts/test_printers_common.py
>>>> b/scripts/test_printers_common.py
>>>> index 73ca525556..d74a8b4d4b 100644
>>>> --- a/scripts/test_printers_common.py
>>>> +++ b/scripts/test_printers_common.py
>>>> @@ -171,6 +171,9 @@ def init_test(test_bin, printer_files,
>>>> printer_names):
>>>> Â Â Â Â Â # Finally, load the test binary.
>>>> Â Â Â Â Â test('file {0}'.format(test_bin))
>>>>
>>>> +Â Â Â # Disable lock elision.
>>>> +Â Â Â test('set environment GLIBC_TUNABLES glibc.elision.enable=0')
>>>> +
>>>> Â Â def go_to_main():
>>>> Â Â Â Â Â """Executes a gdb 'start' command, which takes us to main."""
>>>
>>> Someone would have to confirm on at least one other arch to make sure
>>> this works
>>> as expected.
>>>
>>
>> PING.
>> Is there anybody with an intel / power lock-elision machine who can
>> test this?
>>
>
> PING
>
PING
next prev parent reply other threads:[~2018-04-18 6:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-28 11:58 Stefan Liebler
2018-03-28 13:15 ` Carlos O'Donell
2018-04-05 6:43 ` Stefan Liebler
2018-04-12 13:54 ` Stefan Liebler
2018-04-18 6:26 ` Stefan Liebler [this message]
2018-04-18 14:40 ` Tulio Magno Quites Machado Filho
2018-04-19 10:50 ` 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=c99f80dc-aa0d-30a2-0f8f-8e2f9b5763c7@linux.vnet.ibm.com \
--to=stli@linux.vnet.ibm.com \
--cc=adhemerval.zanella@linaro.org \
--cc=ak@linux.intel.com \
--cc=libc-alpha@sourceware.org \
--cc=martin.galvan@tallertechnologies.com \
--cc=raji@linux.vnet.ibm.com \
--cc=tuliom@linux.vnet.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).