From: Peter Zijlstra <peterz@infradead.org>
To: "Matthew Wilcox (Oracle)" <willy@infradead.org>
Cc: 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>,
Daniel Bristot de Oliveira <bristot@redhat.com>,
Valentin Schneider <vschneid@redhat.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] sched: Make const-safe
Date: Wed, 14 Dec 2022 10:11:01 +0100 [thread overview]
Message-ID: <Y5mTJVi2PBix+Gy6@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <20221212144946.2657785-1-willy@infradead.org>
On Mon, Dec 12, 2022 at 02:49:46PM +0000, Matthew Wilcox (Oracle) wrote:
> With a modified container_of() that preserves constness, the compiler
> finds some pointers which should have been marked as const. task_of()
> also needs to become const-preserving for the !FAIR_GROUP_SCHED case so
> that cfs_rq_of() can take a const argument. No change to generated code.
More const more better I suppose.. Thanks!
Happen to have a sha for the container_of() commit handy?
next prev parent reply other threads:[~2022-12-14 9:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-12 14:49 [PATCH v2] sched: Make const-safe Matthew Wilcox (Oracle)
2022-12-14 9:11 ` Peter Zijlstra [this message]
2022-12-14 18:03 ` Matthew Wilcox
2022-12-16 10:46 ` Peter Zijlstra
2022-12-20 12:59 ` Peter Zijlstra
2022-12-27 12:13 ` [tip: sched/core] " tip-bot2 for Matthew Wilcox (Oracle)
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=Y5mTJVi2PBix+Gy6@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bristot@redhat.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=vincent.guittot@linaro.org \
--cc=vschneid@redhat.com \
--cc=willy@infradead.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