From: K Prateek Nayak <kprateek.nayak@amd.com>
To: Borislav Petkov <bp@alien8.de>
Cc: linux-kernel@vger.kernel.org, linux-tip-commits@vger.kernel.org,
Leon Romanovsky <leon@kernel.org>,
Valentin Schneider <vschneid@redhat.com>,
"Peter Zijlstra (Intel)" <peterz@infradead.org>,
Steve Wahl <steve.wahl@hpe.com>,
x86@kernel.org
Subject: Re: [tip: sched/urgent] sched/fair: Use sched_domain_span() for topology_span_sane()
Date: Mon, 7 Jul 2025 08:56:04 +0530 [thread overview]
Message-ID: <5990b258-2963-4a0a-95f3-db02676d60ea@amd.com> (raw)
In-Reply-To: <20250704123307.GCaGfKAzoceu9siXCN@fat_crate.local>
Hello Boris,
On 7/4/2025 6:03 PM, Borislav Petkov wrote:
>> diff --git a/kernel/sched/topology.c b/kernel/sched/topology.c
>> index 0e46068acb0a..cce540fe36c6 100644
>> --- a/kernel/sched/topology.c
>> +++ b/kernel/sched/topology.c
>> @@ -2423,6 +2423,14 @@ static bool topology_span_sane(const struct cpumask *cpu_map)
>> struct cpumask *sd_span = sched_domain_span(sd);
>> int id;
>> + /*
>> + * If the child already covers the cpumap, sd
>> + * remains un-initialized. Use sd->private to
>> + * detect uninitialized domains.
>> + */
>> + if (!sd->private)
>> + continue;
>> +
>> /* lowest bit set in this mask is used as a unique id */
>> id = cpumask_first(sd_span);
>> ---
>
> Yeah, when you send a hunk I should apply, no matter how easy it is, pls send
> it from a mail client which doesn't mangle the diff otherwise I get:
>
> $ test-apply.sh -n /tmp/diff
> checking file kernel/sched/topology.c
> Hunk #1 FAILED at 2423.
> 1 out of 1 hunk FAILED
>
> Or you can attach it.
>
> I've done it by hand now.
Thank you for the testing and sorry about the malformed diff! I'll
double (and triple) check next time before sending. Thanks a ton for
applying it manually.
--
Thanks and Regards,
Prateek
prev parent reply other threads:[~2025-07-07 3:26 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 6:10 [PATCH v2] " K Prateek Nayak
2025-06-30 14:39 ` Steve Wahl
2025-07-03 16:00 ` Valentin Schneider
2025-07-04 9:13 ` [tip: sched/urgent] " tip-bot2 for K Prateek Nayak
2025-07-04 10:21 ` Borislav Petkov
2025-07-04 10:32 ` Peter Zijlstra
2025-07-04 11:46 ` K Prateek Nayak
2025-07-04 12:33 ` Borislav Petkov
2025-07-07 3:26 ` K Prateek Nayak [this message]
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=5990b258-2963-4a0a-95f3-db02676d60ea@amd.com \
--to=kprateek.nayak@amd.com \
--cc=bp@alien8.de \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=steve.wahl@hpe.com \
--cc=vschneid@redhat.com \
--cc=x86@kernel.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
all inboxes | Powered by JetHome®