From: Naman Jain <namjain@linux.microsoft.com>
To: Valentin Schneider <vschneid@redhat.com>,
Ingo Molnar <mingo@redhat.com>,
Peter Zijlstra <peterz@infradead.org>,
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>
Cc: stable@vger.kernel.org, linux-kernel@vger.kernel.org,
Steve Wahl <steve.wahl@hpe.com>,
Saurabh Singh Sengar <ssengar@linux.microsoft.com>,
srivatsa@csail.mit.edu, K Prateek Nayak <kprateek.nayak@amd.com>,
Michael Kelley <mhklinux@outlook.com>,
Shrikanth Hegde <sshegde@linux.ibm.com>
Subject: Re: [PATCH v5] sched/topology: Enable topology_span_sane check only for debug builds
Date: Wed, 12 Mar 2025 12:37:43 +0530 [thread overview]
Message-ID: <16004c77-de73-4208-9a10-feee7225e738@linux.microsoft.com> (raw)
In-Reply-To: <xhsmh34fjr3av.mognet@vschneid-thinkpadt14sgen2i.remote.csb>
On 3/11/2025 9:02 PM, Valentin Schneider wrote:
> On 10/03/25 10:55, Naman Jain wrote:
>> From: Saurabh Sengar <ssengar@linux.microsoft.com>
>>
>> On a x86 system under test with 1780 CPUs, topology_span_sane() takes
>> around 8 seconds cumulatively for all the iterations. It is an expensive
>> operation which does the sanity of non-NUMA topology masks.
>>
>> CPU topology is not something which changes very frequently hence make
>> this check optional for the systems where the topology is trusted and
>> need faster bootup.
>>
>> Restrict this to sched_verbose kernel cmdline option so that this penalty
>> can be avoided for the systems who want to avoid it.
>>
>> Cc: stable@vger.kernel.org
>> Fixes: ccf74128d66c ("sched/topology: Assert non-NUMA topology masks don't (partially) overlap")
>> Signed-off-by: Saurabh Sengar <ssengar@linux.microsoft.com>
>> Co-developed-by: Naman Jain <namjain@linux.microsoft.com>
>> Signed-off-by: Naman Jain <namjain@linux.microsoft.com>
>> Tested-by: K Prateek Nayak <kprateek.nayak@amd.com>
>> ---
>> Changes since v4:
>> https://lore.kernel.org/all/20250306055354.52915-1-namjain@linux.microsoft.com/
>> - Rephrased print statement and moved it to sched_domain_debug.
>> (addressing Valentin's comments)
>> Changes since v3:
>> https://lore.kernel.org/all/20250203114738.3109-1-namjain@linux.microsoft.com/
>> - Minor typo correction in comment
>> - Added Tested-by tag from Prateek for x86
>> Changes since v2:
>> https://lore.kernel.org/all/1731922777-7121-1-git-send-email-ssengar@linux.microsoft.com/
>> - Use sched_debug() instead of using sched_debug_verbose
>> variable directly (addressing Prateek's comment)
>>
>> Changes since v1:
>> https://lore.kernel.org/all/1729619853-2597-1-git-send-email-ssengar@linux.microsoft.com/
>> - Use kernel cmdline param instead of compile time flag.
>>
>> Adding a link to the other patch which is under review.
>> https://lore.kernel.org/lkml/20241031200431.182443-1-steve.wahl@hpe.com/
>> Above patch tries to optimize the topology sanity check, whereas this
>> patch makes it optional. We believe both patches can coexist, as even
>> with optimization, there will still be some performance overhead for
>> this check.
>>
>> ---
>> kernel/sched/topology.c | 9 ++++++++-
>> 1 file changed, 8 insertions(+), 1 deletion(-)
>>
>> diff --git a/kernel/sched/topology.c b/kernel/sched/topology.c
>> index c49aea8c1025..d7254c47af45 100644
>> --- a/kernel/sched/topology.c
>> +++ b/kernel/sched/topology.c
>> @@ -132,8 +132,11 @@ static void sched_domain_debug(struct sched_domain *sd, int cpu)
>> {
>> int level = 0;
>>
>> - if (!sched_debug_verbose)
>> + if (!sched_debug_verbose) {
>> + pr_info_once("%s: Scheduler topology debugging disabled, add 'sched_verbose' to the cmdline to enable it\n",
>> + __func__);
>> return;
>> + }
>>
>
> Nit: I've been told not to break warnings over multiple lines so they can
> be grep'ed, but given this has the "sched_domain_debug:" prefix I think we
> could get away with the below.
>
> Regardless:
> Reviewed-by: Valentin Schneider <vschneid@redhat.com>
>
> ---
> diff --git a/kernel/sched/topology.c b/kernel/sched/topology.c
> index d7254c47af455..b4dc7c7d2c41c 100644
> --- a/kernel/sched/topology.c
> +++ b/kernel/sched/topology.c
> @@ -133,7 +133,8 @@ static void sched_domain_debug(struct sched_domain *sd, int cpu)
> int level = 0;
>
> if (!sched_debug_verbose) {
> - pr_info_once("%s: Scheduler topology debugging disabled, add 'sched_verbose' to the cmdline to enable it\n",
> + pr_info_once("%s: Scheduler topology debugging disabled, "
> + "add 'sched_verbose' to the cmdline to enable it\n",
> __func__);
> return;
> }
Thanks for reviewing. I'll wait a couple more days to push the next
version.
Thanks,
Naman
next prev parent reply other threads:[~2025-03-12 7:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-10 5:25 [PATCH v5] sched/topology: Enable topology_span_sane check only for debug builds Naman Jain
2025-03-11 15:32 ` Valentin Schneider
2025-03-12 7:07 ` Naman Jain [this message]
2025-03-17 9:57 ` Naman Jain
2025-03-17 10:25 ` Valentin Schneider
2025-04-03 6:14 ` Naman Jain
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=16004c77-de73-4208-9a10-feee7225e738@linux.microsoft.com \
--to=namjain@linux.microsoft.com \
--cc=bsegall@google.com \
--cc=dietmar.eggemann@arm.com \
--cc=juri.lelli@redhat.com \
--cc=kprateek.nayak@amd.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mhklinux@outlook.com \
--cc=mingo@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=srivatsa@csail.mit.edu \
--cc=ssengar@linux.microsoft.com \
--cc=sshegde@linux.ibm.com \
--cc=stable@vger.kernel.org \
--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