From: Peter Zijlstra <peterz@infradead.org>
To: K Prateek Nayak <kprateek.nayak@amd.com>
Cc: Ingo Molnar <mingo@redhat.com>,
Juri Lelli <juri.lelli@redhat.com>,
Vincent Guittot <vincent.guittot@linaro.org>,
Valentin Schneider <vschneid@redhat.com>,
Leon Romanovsky <leon@kernel.org>,
linux-kernel@vger.kernel.org, Steve Wahl <steve.wahl@hpe.com>,
Borislav Petkov <bp@alien8.de>,
Dietmar Eggemann <dietmar.eggemann@arm.com>,
Steven Rostedt <rostedt@goodmis.org>,
Ben Segall <bsegall@google.com>, Mel Gorman <mgorman@suse.de>,
srikar@linux.vnet.ibm.com, hca@linux.ibm.com
Subject: Re: [PATCH v5] sched/fair: Use sched_domain_span() for topology_span_sane()
Date: Mon, 25 Aug 2025 13:16:27 +0200 [thread overview]
Message-ID: <20250825111627.GW3245006@noisy.programming.kicks-ass.net> (raw)
In-Reply-To: <5940cd15-b207-416a-b4e4-b5953f4cbf47@amd.com>
On Mon, Aug 25, 2025 at 04:17:52PM +0530, K Prateek Nayak wrote:
> The above helpers may need guarding behind CONFIG_SCHED_{SMT,CLUSTER,MC}
> if I'm not mistaken. Possibility for some unification and cleanup with:
>
> Thoughts?
I hate we need __maybe_unused on static inline functions, but yeah, that
might be nicer.
Can you fold the lot and stick that nice Changelog on? Then I'll get it
into sched/core and we can forget all about this stuff.
next prev parent reply other threads:[~2025-08-25 11:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 4:08 K Prateek Nayak
2025-08-25 9:19 ` Peter Zijlstra
2025-08-25 10:47 ` K Prateek Nayak
2025-08-25 11:16 ` Peter Zijlstra [this message]
2025-08-25 12:16 ` K Prateek Nayak
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=20250825111627.GW3245006@noisy.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=bp@alien8.de \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=hca@linux.ibm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@redhat.com \
--cc=rostedt@goodmis.org \
--cc=srikar@linux.vnet.ibm.com \
--cc=steve.wahl@hpe.com \
--cc=vincent.guittot@linaro.org \
--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®