From: Peter Zijlstra <peterz@infradead.org>
To: Mathieu Desnoyers <mathieu.desnoyers@efficios.com>
Cc: "David Laight" <David.Laight@aculab.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Paul E . McKenney" <paulmck@kernel.org>,
"Boqun Feng" <boqun.feng@gmail.com>,
"H . Peter Anvin" <hpa@zytor.com>, "Paul Turner" <pjt@google.com>,
"linux-api@vger.kernel.org" <linux-api@vger.kernel.org>,
"Christian Brauner" <brauner@kernel.org>,
"Florian Weimer" <fw@deneb.enyo.de>,
"carlos@redhat.com" <carlos@redhat.com>,
"Peter Oskolkov" <posk@posk.io>,
"Alexander Mikhalitsyn" <alexander@mihalicyn.com>,
"Chris Kennelly" <ckennelly@google.com>,
"Ingo Molnar" <mingo@redhat.com>,
"Darren Hart" <dvhart@infradead.org>,
"Davidlohr Bueso" <dave@stgolabs.net>,
"André Almeida" <andrealmeid@igalia.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
"Steven Rostedt" <rostedt@goodmis.org>,
"Jonathan Corbet" <corbet@lwn.net>,
"Noah Goldstein" <goldstein.w.n@gmail.com>,
"Daniel Colascione" <dancol@google.com>,
"longman@redhat.com" <longman@redhat.com>,
"Florian Weimer" <fweimer@redhat.com>
Subject: Re: [RFC PATCH v2 1/4] rseq: Add sched_state field to struct rseq
Date: Thu, 28 Sep 2023 16:26:28 +0200 [thread overview]
Message-ID: <20230928142628.GC27245@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <34ddb730-8893-19a8-00fe-84c4e281eef1@efficios.com>
On Thu, Sep 28, 2023 at 09:20:36AM -0400, Mathieu Desnoyers wrote:
> Of course things are more complicated with PI-futex, is that what you have
> in mind ?
PI futex has to go through the kernel, also, they already spin-wait on
owner.
next prev parent reply other threads:[~2023-09-28 14:27 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-29 19:14 [RFC PATCH v2 0/4] Extend rseq with sched_state_ptr field Mathieu Desnoyers
2023-05-29 19:14 ` [RFC PATCH v2 1/4] rseq: Add sched_state field to struct rseq Mathieu Desnoyers
2023-05-29 19:35 ` Florian Weimer
2023-05-29 19:48 ` Mathieu Desnoyers
2023-05-30 8:20 ` Florian Weimer
2023-05-30 14:25 ` Mathieu Desnoyers
2023-05-30 15:13 ` Mathieu Desnoyers
2023-09-26 20:52 ` Dmitry Vyukov
2023-09-26 23:49 ` Dmitry Vyukov
2023-09-26 23:54 ` Dmitry Vyukov
2023-09-27 4:51 ` Florian Weimer
2023-09-27 15:58 ` Dmitry Vyukov
2023-09-28 8:52 ` Florian Weimer
2023-09-28 14:44 ` Dmitry Vyukov
2023-09-28 14:47 ` Dmitry Vyukov
2023-09-28 10:39 ` Peter Zijlstra
2023-09-28 11:22 ` David Laight
2023-09-28 13:20 ` Mathieu Desnoyers
2023-09-28 14:26 ` Peter Zijlstra [this message]
2023-09-28 14:33 ` David Laight
2023-09-28 15:05 ` André Almeida
2023-09-28 14:43 ` Steven Rostedt
2023-09-28 15:51 ` David Laight
2023-10-02 16:51 ` Steven Rostedt
2023-10-02 17:22 ` David Laight
2023-10-02 17:56 ` Steven Rostedt
2023-09-28 20:21 ` Thomas Gleixner
2023-09-28 20:43 ` Mathieu Desnoyers
2023-09-28 20:54 ` Thomas Gleixner
2023-09-28 22:11 ` Mathieu Desnoyers
2023-05-29 19:14 ` [RFC PATCH v2 2/4] selftests/rseq: Add sched_state rseq field and getter Mathieu Desnoyers
2023-05-29 19:14 ` [RFC PATCH v2 3/4] selftests/rseq: Implement sched state test program Mathieu Desnoyers
2023-05-29 19:14 ` [RFC PATCH v2 4/4] selftests/rseq: Implement rseq_mutex " Mathieu Desnoyers
2023-09-28 19:55 ` Thomas Gleixner
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=20230928142628.GC27245@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=David.Laight@aculab.com \
--cc=alexander@mihalicyn.com \
--cc=andrealmeid@igalia.com \
--cc=boqun.feng@gmail.com \
--cc=brauner@kernel.org \
--cc=carlos@redhat.com \
--cc=ckennelly@google.com \
--cc=corbet@lwn.net \
--cc=dancol@google.com \
--cc=dave@stgolabs.net \
--cc=dvhart@infradead.org \
--cc=fw@deneb.enyo.de \
--cc=fweimer@redhat.com \
--cc=goldstein.w.n@gmail.com \
--cc=hpa@zytor.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@redhat.com \
--cc=paulmck@kernel.org \
--cc=pjt@google.com \
--cc=posk@posk.io \
--cc=rostedt@goodmis.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 NNTP newsgroup(s).