From: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
To: Quchaosheng <quchaosheng000406@163.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
John Stultz <jstultz@google.com>,
Valentin Schneider <vschneid@redhat.com>,
Waiman Long <longman@redhat.com>,
Boqun Feng <boqun.kernel@gmail.com>,
Will Deacon <will@kernel.org>, Thomas Gleixner <tglx@kernel.org>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
K Prateek Nayak <kprateek.nayak@amd.com>,
linux-kernel@vger.kernel.org, linux-rt-users@vger.kernel.org
Subject: Re: [PATCH] sched/proxy: allow SCHED_PROXY_EXEC with PREEMPT_RT
Date: Mon, 21 Sep 2026 12:09:21 +0200 [thread overview]
Message-ID: <20260921100921.PsZhWgmh@linutronix.de> (raw)
In-Reply-To: <20260921081525.2982361-1-quchaosheng000406@163.com>
On 2026-09-21 16:15:25 [+0800], Quchaosheng wrote:
> Note that this makes the combination build and boot; it does not make
> proxy execution actually do anything useful on PREEMPT_RT. An rt_mutex
> already provides priority inheritance, so there is no blocked_on chain to
> follow and proxy execution stays inactive. Replacing rt_mutexes in the RT
> mutex implementation is tracked as future work in the proxy execution
> series.
Why exactly is this a good thing to do?
> Signed-off-by: Quchaosheng <quchaosheng000406@163.com>
Sebastian
next prev parent reply other threads:[~2026-09-21 10:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-21 8:15 Quchaosheng
2026-09-21 10:09 ` Sebastian Andrzej Siewior [this message]
2026-09-21 10:51 ` Quchaosheng
2026-09-21 12:57 ` Sebastian Andrzej Siewior
2026-09-22 7:06 ` [PATCH v2] " Quchaosheng
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=20260921100921.PsZhWgmh@linutronix.de \
--to=bigeasy@linutronix.de \
--cc=boqun.kernel@gmail.com \
--cc=jstultz@google.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rt-users@vger.kernel.org \
--cc=longman@redhat.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=quchaosheng000406@163.com \
--cc=tglx@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=will@kernel.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
all inboxes | Powered by JetHome®