From: Peter Zijlstra <peterz@infradead.org>
To: Breno Leitao <leitao@debian.org>
Cc: Andrea Righi <arighi@nvidia.com>, Tejun Heo <tj@kernel.org>,
David Vernet <void@manifault.com>,
Changwoo Min <changwoo@igalia.com>,
Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
Valentin Schneider <vschneid@redhat.com>,
sched-ext@lists.linux.dev, linux-kernel@vger.kernel.org,
kernel-team@meta.com, jake@hillion.co.uk
Subject: Re: [PATCH] sched/ext: Suppress warning in __this_cpu_write() by disabling preemption
Date: Wed, 16 Jul 2025 15:40:43 +0200 [thread overview]
Message-ID: <20250716134043.GA905792@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <d2ocjfutd6o6euvjhln5tj4sdnmlblgpy2papponnumtu5slcx@tfc6y5webosm>
On Wed, Jul 16, 2025 at 06:20:02AM -0700, Breno Leitao wrote:
> Hello Peter,
>
> On Wed, Jul 16, 2025 at 03:15:12PM +0200, Andrea Righi wrote:
> > On Wed, Jul 16, 2025 at 02:51:28PM +0200, Peter Zijlstra wrote:
> > > Also, I don't seem to have this scx_layered
>
> This is a rust scheduler that could be found at
> https://github.com/sched-ext/scx/tree/main/scheds/rust/scx_layered
Well, that just means the Changelog is entirely useless. Please always
refer to in-tree code when describing a problem.
next prev parent reply other threads:[~2025-07-16 13:40 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-16 12:46 Breno Leitao
2025-07-16 12:51 ` Peter Zijlstra
2025-07-16 13:15 ` Andrea Righi
2025-07-16 13:20 ` Breno Leitao
2025-07-16 13:40 ` Peter Zijlstra [this message]
2025-07-16 13:36 ` Peter Zijlstra
2025-07-16 14:26 ` Andrea Righi
2025-07-16 15:49 ` Peter Zijlstra
2025-07-16 16:08 ` Breno Leitao
2025-07-16 16:13 ` Andrea Righi
2025-07-16 12:54 ` Steven Rostedt
2025-07-16 13:06 ` Peter Zijlstra
2025-07-16 13:20 ` Andrea Righi
2025-07-16 13:33 ` Peter Zijlstra
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=20250716134043.GA905792@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=arighi@nvidia.com \
--cc=bsegall@google.com \
--cc=changwoo@igalia.com \
--cc=dietmar.eggemann@arm.com \
--cc=jake@hillion.co.uk \
--cc=juri.lelli@redhat.com \
--cc=kernel-team@meta.com \
--cc=leitao@debian.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=sched-ext@lists.linux.dev \
--cc=tj@kernel.org \
--cc=vincent.guittot@linaro.org \
--cc=void@manifault.com \
--cc=vschneid@redhat.com \
/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®