From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Valentin Schneider <vschneid@redhat.com>,
Peter Zijlstra <peterz@infradead.org>
Cc: Naman Jain <namjain@linux.microsoft.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>,
<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>, Michael Kelley <mhklinux@outlook.com>
Subject: Re: [PATCH v3] sched/topology: Enable topology_span_sane check only for debug builds
Date: Fri, 7 Feb 2025 08:14:10 +0530 [thread overview]
Message-ID: <6d436d56-20f7-4106-bedc-e9d146427fa9@amd.com> (raw)
In-Reply-To: <xhsmhed0bjdum.mognet@vschneid-thinkpadt14sgen2i.remote.csb>
Hello Valentin,
On 2/6/2025 8:54 PM, Valentin Schneider wrote:
> [..snip..]
>> So circling back to my original question around "SDTL_ARCH_VERIFIED",
>> would folks be okay to an early bailout from topology_span_sane() on:
>>
>> if (!sched_debug() && (tl->flags & SDTL_ARCH_VERIFIED))
>> return;
>>
>> and more importantly, do folks care enough about topology_span_sane()
>> to have it run on other architectures and not just have it guarded
>> behind just "sched_debug()" which starts off as false by default?
>>
>
> If/when possible I prefer to have sanity checks run unconditionally, as
> long as they don't noticeably impact runtime. Unfortunately this does show
> up in the boot time, though Steve had a promising improvement for that.
>
> Anyway, if someone gets one of those hangs on a
>
> do { } while (group != sd->groups)
>
> they'll quickly turn on sched_verbose (or be told to) and the sanity check
> will holler at them, so I'm not entirely against it.
If you're game, I'm too!
I just put it out there in case folks had any strong feelings against
this on other arch but that doesn't seem to be the case and we all love
a simple solution :)
>
>> (Sorry for the long answer explaining my thought process.)
>>
>>>
>>> That I can't remember, sorry :/
>>
>> --
>> Thanks and Regards,
>> Prateek
>
--
Thanks and Regards,
Prateek
next prev parent reply other threads:[~2025-02-07 2:46 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-03 11:47 [PATCH v3] sched/topology: Enable topology_span_sane check only for debug builds Naman Jain
2025-02-05 7:20 ` K Prateek Nayak
2025-02-05 7:23 ` Naman Jain
2025-02-10 9:53 ` Naman Jain
2025-02-05 9:48 ` K Prateek Nayak
2025-02-05 9:55 ` Peter Zijlstra
2025-02-05 10:13 ` K Prateek Nayak
2025-02-05 10:16 ` Peter Zijlstra
2025-02-06 9:10 ` K Prateek Nayak
2025-02-06 9:47 ` Naman Jain
2025-02-06 10:19 ` K Prateek Nayak
2025-02-06 10:55 ` Naman Jain
2025-02-06 15:24 ` Valentin Schneider
2025-02-06 15:30 ` Steve Wahl
2025-02-06 17:18 ` Naman Jain
2025-02-07 2:44 ` K Prateek Nayak [this message]
2025-02-11 5:52 ` Shrikanth Hegde
2025-02-11 7:06 ` Naman Jain
2025-02-11 10:56 ` 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=6d436d56-20f7-4106-bedc-e9d146427fa9@amd.com \
--to=kprateek.nayak@amd.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=mhklinux@outlook.com \
--cc=mingo@redhat.com \
--cc=namjain@linux.microsoft.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=srivatsa@csail.mit.edu \
--cc=ssengar@linux.microsoft.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.