From: Joseph Myers <joseph@codesourcery.com>
To: Kurt Kanzenbach <kurt@linutronix.de>
Cc: <libc-alpha@sourceware.org>, Florian Weimer <fweimer@redhat.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: [PATCH RFC 3/3] nptl: Include CLOCK_MONOTONIC in mutex tests
Date: Mon, 21 Jun 2021 20:07:39 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2106212006230.1010016@digraph.polyomino.org.uk> (raw)
In-Reply-To: <20210621111650.1164689-4-kurt@linutronix.de>
On Mon, 21 Jun 2021, Kurt Kanzenbach via Libc-alpha wrote:
> diff --git a/sysdeps/unix/sysv/linux/kernel-features.h b/sysdeps/unix/sysv/linux/kernel-features.h
> index 1680b10ca1b6..eb5c4d5a04bd 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 >= 0x051400
0x051400 is 5.20.0, not 5.14.0.
I'd expect this change to appear in an earlier patch, with
__ASSUME_FUTEX_LOCK_PI2 conditionals being used to disable fallback
support for kernels found at runtime not to support the new feature.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-06-21 20:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-21 11:16 [PATCH RFC 0/3] nptl: Introduce and use FUTEX_LOCK_PI2 Kurt Kanzenbach
2021-06-21 11:16 ` [PATCH RFC 1/3] nptl: Introduce futex_lock_pi2() Kurt Kanzenbach
2021-06-21 11:16 ` [PATCH RFC 2/3] nptl: Use futex_lock_pi2() Kurt Kanzenbach
2021-06-21 11:16 ` [PATCH RFC 3/3] nptl: Include CLOCK_MONOTONIC in mutex tests Kurt Kanzenbach
2021-06-21 20:07 ` Joseph Myers [this message]
2021-06-22 8:58 ` Kurt Kanzenbach
2021-06-21 21:32 ` [PATCH RFC 0/3] nptl: Introduce and use FUTEX_LOCK_PI2 Adhemerval Zanella
2021-06-22 7:26 ` Kurt Kanzenbach
2021-06-22 7:29 ` Florian Weimer
2021-06-22 8:55 ` Kurt Kanzenbach
2021-06-22 12:30 ` Adhemerval Zanella
2021-06-22 14:25 ` Kurt Kanzenbach
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=alpine.DEB.2.22.394.2106212006230.1010016@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=bigeasy@linutronix.de \
--cc=fweimer@redhat.com \
--cc=kurt@linutronix.de \
--cc=libc-alpha@sourceware.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).