From: Adhemerval Zanella via Libc-alpha <libc-alpha@sourceware.org>
To: Kurt Kanzenbach <kurt@linutronix.de>, libc-alpha@sourceware.org
Cc: Florian Weimer <fweimer@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Peter Zijlstra <peterz@infradead.org>,
Thomas Gleixner <tglx@linutronix.de>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: [PATCH v1 1/6] Linux: Add FUTEX_LOCK_PI2
Date: Fri, 9 Jul 2021 10:32:41 -0300 [thread overview]
Message-ID: <8ae1ee9f-c5c6-0266-a839-a17e4e88be65@linaro.org> (raw)
In-Reply-To: <20210625081104.1134598-2-kurt@linutronix.de>
On 25/06/2021 05:10, Kurt Kanzenbach wrote:
> Linux v5.14.0 introduced a new futex operation called FUTEX_LOCK_PI2.
>
> This kernel feature can be used to implement
> pthread_mutex_clocklock(MONOTONIC)/PI.
>
> Signed-off-by: Kurt Kanzenbach <kurt@linutronix.de>
The __LINUX_KERNEL_VERSION looks fine now.
You will need to check with Carlos O'Donell if this is suitable for 2.34.
Reviewed-by: Adhemerval Zanella <adhemerval.zanella@linaro.org>
> ---
> sysdeps/unix/sysv/linux/kernel-features.h | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/sysdeps/unix/sysv/linux/kernel-features.h b/sysdeps/unix/sysv/linux/kernel-features.h
> index 1680b10ca1b6..af4b2b304715 100644
> --- a/sysdeps/unix/sysv/linux/kernel-features.h
> +++ b/sysdeps/unix/sysv/linux/kernel-features.h
> @@ -218,4 +218,12 @@
> # define __ASSUME_FACCESSAT2 0
> #endif
>
> +/* The FUTEX_LOCK_PI2 operation was introduced across all architectures in Linux
> + 5.14. */
> +#if __LINUX_KERNEL_VERSION >= 0x050e00
> +# define __ASSUME_FUTEX_LOCK_PI2 1
> +#else
> +# define __ASSUME_FUTEX_LOCK_PI2 0
> +#endif
> +
> #endif /* kernel-features.h */
>
next prev parent reply other threads:[~2021-07-09 13:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-25 8:10 [PATCH v1 0/6] nptl: Introduce and use FUTEX_LOCK_PI2 Kurt Kanzenbach via Libc-alpha
2021-06-25 8:10 ` [PATCH v1 1/6] Linux: Add FUTEX_LOCK_PI2 Kurt Kanzenbach via Libc-alpha
2021-07-09 13:32 ` Adhemerval Zanella via Libc-alpha [this message]
2021-06-25 8:11 ` [PATCH v1 2/6] nptl: Introduce futex_lock_pi2() Kurt Kanzenbach via Libc-alpha
2021-07-09 14:13 ` Adhemerval Zanella via Libc-alpha
2021-06-25 8:11 ` [PATCH v1 3/6] nptl: Use futex_lock_pi2() Kurt Kanzenbach via Libc-alpha
2021-07-09 14:21 ` Adhemerval Zanella via Libc-alpha
2021-06-25 8:11 ` [PATCH v1 4/6] nptl: Remove mutex test 10 Kurt Kanzenbach via Libc-alpha
2021-07-09 14:23 ` Adhemerval Zanella via Libc-alpha
2021-06-25 8:11 ` [PATCH v1 5/6] nptl: mutex-test5: Include CLOCK_MONOTONIC for PI Kurt Kanzenbach via Libc-alpha
2021-06-25 8:11 ` [PATCH v1 6/6] nptl: mutex-test9: " Kurt Kanzenbach via Libc-alpha
2021-07-09 6:57 ` [PATCH v1 0/6] nptl: Introduce and use FUTEX_LOCK_PI2 Kurt Kanzenbach via Libc-alpha
2021-07-09 13:30 ` Adhemerval Zanella via Libc-alpha
2021-07-09 14:20 ` Kurt Kanzenbach via Libc-alpha
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=8ae1ee9f-c5c6-0266-a839-a17e4e88be65@linaro.org \
--to=libc-alpha@sourceware.org \
--cc=adhemerval.zanella@linaro.org \
--cc=bigeasy@linutronix.de \
--cc=fweimer@redhat.com \
--cc=joseph@codesourcery.com \
--cc=kurt@linutronix.de \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
/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).