From: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
To: libc-alpha@sourceware.org
Subject: Re: [PATCH v3 0/4] Add CLOCK_MONOTONIC support for PI mutexes
Date: Fri, 1 Oct 2021 08:42:31 -0300 [thread overview]
Message-ID: <4e8c341d-cf42-7f05-afb3-4b02b09a13af@linaro.org> (raw)
In-Reply-To: <a696af75-41c4-e59c-be14-8c4d8fdc50a6@linaro.org>
I will push this set shortly if no one opposes it.
On 27/09/2021 10:48, Adhemerval Zanella wrote:
> Ping on the set.
>
> On 06/09/2021 17:47, Adhemerval Zanella wrote:
>> It adds support for CLOCK_MONOTONIC for PI mutexes by using the new
>> Linux v5.14 FUTEX_LOCK_PI2 operation. Similar to current approach,
>> pthread_mutex_clocklock might return EINVAL if the underlying kernel
>> has no support for the futex operation.
>>
>> Changes since v2:
>>
>> * Renamed xpthread_mutex_pi_support_monotonic to
>> support_mutex_pi_monotonic.
>>
>> Changes since v1:
>>
>> * Refactor futex_lock_pi64 and avoid adding futex_lock_pi2. The
>> FUTEX_LOCK_PI2 logic is done at only one place, so the code change
>> on pthread routines are minimal. Also, FUTEX_LOCK_PI2 is only
>> used if it is really required, i.e, when a timeout against
>> CLOCK_MONOTONIC is used.
>> * Do not remove nptl/tst-mutexpi10.c, but instead adjust it to new
>> FUTEX_LOCK_PI2 support.
>> * Add pthread_mutex_pi_support_monotonic() to check if monotonic
>> clock with PI mutexes are supported and use on test to check for
>> the expected result.
>>
>> Adhemerval Zanella (3):
>> nptl: Use FUTEX_LOCK_PI2 when available
>> support: Add support_mutex_pi_monotonic
>> nptl: Add CLOCK_MONOTONIC support for PI mutexes
>>
>> Kurt Kanzenbach (1):
>> Linux: Add FUTEX_LOCK_PI2
>>
>> nptl/futex-internal.c | 63 +++++++++++++++++++++++
>> nptl/pthread_mutex_lock.c | 3 +-
>> nptl/pthread_mutex_timedlock.c | 10 +---
>> nptl/tst-mutexpi10.c | 42 +++++++++------
>> support/Makefile | 1 +
>> support/support_mutex_pi_monotonic.c | 33 ++++++++++++
>> support/xthread.h | 4 ++
>> sysdeps/nptl/futex-internal.h | 58 ++-------------------
>> sysdeps/nptl/lowlevellock-futex.h | 1 +
>> sysdeps/pthread/tst-mutex5.c | 23 ++++++---
>> sysdeps/pthread/tst-mutex9.c | 20 ++++---
>> sysdeps/unix/sysv/linux/kernel-features.h | 8 +++
>> 12 files changed, 172 insertions(+), 94 deletions(-)
>> create mode 100644 support/support_mutex_pi_monotonic.c
>>
prev parent reply other threads:[~2021-10-01 11:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-06 20:47 [PATCH v3 0/4] Add CLOCK_MONOTONIC support for PI mutexes Adhemerval Zanella via Libc-alpha
2021-09-06 20:47 ` [PATCH v3 1/4] Linux: Add FUTEX_LOCK_PI2 Adhemerval Zanella via Libc-alpha
2021-09-06 20:47 ` [PATCH v3 2/4] nptl: Use FUTEX_LOCK_PI2 when available Adhemerval Zanella via Libc-alpha
2021-09-06 20:47 ` [PATCH v3 3/4] support: Add support_mutex_pi_monotonic Adhemerval Zanella via Libc-alpha
2021-09-06 20:47 ` [PATCH v3 4/4] nptl: Add CLOCK_MONOTONIC support for PI mutexes Adhemerval Zanella via Libc-alpha
2021-09-27 13:48 ` [PATCH v3 0/4] " Adhemerval Zanella via Libc-alpha
2021-10-01 11:42 ` Adhemerval Zanella via Libc-alpha [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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4e8c341d-cf42-7f05-afb3-4b02b09a13af@linaro.org \
--to=libc-alpha@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
/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).