From: Naman Jain <namjain@linux.microsoft.com>
To: K Prateek Nayak <kprateek.nayak@amd.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>,
Valentin Schneider <vschneid@redhat.com>
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, Michael Kelley <mhklinux@outlook.com>,
namjain@linux.microsoft.com
Subject: Re: [PATCH v3] sched/topology: Enable topology_span_sane check only for debug builds
Date: Mon, 10 Feb 2025 15:23:19 +0530 [thread overview]
Message-ID: <d3884226-b145-4960-b5c8-ca8284aff9ef@linux.microsoft.com> (raw)
In-Reply-To: <ee7f3c75-b7f6-416b-b6e6-983c466f1c83@linux.microsoft.com>
On 2/5/2025 12:53 PM, Naman Jain wrote:
>
>
> On 2/5/2025 12:50 PM, K Prateek Nayak wrote:
>> Hello Naman,
>>
>> On 2/3/2025 5:17 PM, Naman Jain wrote:
>>> From: Saurabh Sengar <ssengar@linux.microsoft.com>
>>>
>>> On a x86 system under test with 1780 CPUs, topology_span_sane() takes
>
> <.>
>
>>> {
>>> int i = cpu + 1;
>>> + /* Skip the topology sanity check for non-debug, as it is a
>>> time- consuming operatin */
>>
>> s/operatin/operation/
>>
>>> + if (!sched_debug()) {
>>> + pr_info_once("%s: Skipping topology span sanity check. Use
>>> `sched_verbose` boot parameter to enable it.\n",
>>
>> This could be broken down as follows:
>>
>> pr_info_once("%s: Skipping topology span sanity check."
>> " Use `sched_verbose` boot parameter to enable it.\n",
>> __func__);
>>
>> Running:
>>
>> grep -r -A 5 "pr_info(.*[^;,]$" kernel/
>>
>> gives similar usage across kernel/*. Apart from those nits, feel
>> free to add:
>>
>> Tested-by: K Prateek Nayak <kprateek.nayak@amd.com> # x86
>>
>> if the future version does not change much.
>>
>
> Hello Prateek,
> Thanks for reviewing and testing this. I'll make changes based on your
> feedback in next version.
>
> Regards,
> Naman
>
Hi Prateek,
After breaking down the print msg based on your suggestion, checkpatch
gives a warning. There are no warnings reported with current version of
change. Even the fix suggested by checkpatch is aligned to what we have
right now. So I'll keep it like this, not push further changes as of now
and wait for the maintainers to pick the patch.
WARNING: quoted string split across lines
#57: FILE: kernel/sched/topology.c:2365:
+ pr_info_once("%s: Skipping topology span sanity check."
+ " Use `sched_verbose` boot parameter to
enable it.\n",
total: 0 errors, 1 warnings, 14 lines checked
Regards,
Naman
next prev parent reply other threads:[~2025-02-10 9:53 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 [this message]
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
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=d3884226-b145-4960-b5c8-ca8284aff9ef@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=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