From: "tip-bot2 for Yury Norov" <tip-bot2@linutronix.de>
To: linux-tip-commits@vger.kernel.org
Cc: Yury Norov <yury.norov@gmail.com>, Ingo Molnar <mingo@kernel.org>,
Mel Gorman <mgorman@suse.de>,
x86@kernel.org, linux-kernel@vger.kernel.org
Subject: [tip: sched/core] sched/topology: Fix sched_numa_find_nth_cpu() in non-NUMA case
Date: Fri, 15 Sep 2023 12:03:27 -0000 [thread overview]
Message-ID: <169477940797.27769.5804988700503210268.tip-bot2@tip-bot2> (raw)
In-Reply-To: <20230819141239.287290-5-yury.norov@gmail.com>
The following commit has been merged into the sched/core branch of tip:
Commit-ID: 8ab63d418d4339d996f80d02a00dbce0aa3ff972
Gitweb: https://git.kernel.org/tip/8ab63d418d4339d996f80d02a00dbce0aa3ff972
Author: Yury Norov <yury.norov@gmail.com>
AuthorDate: Sat, 19 Aug 2023 07:12:36 -07:00
Committer: Ingo Molnar <mingo@kernel.org>
CommitterDate: Fri, 15 Sep 2023 13:48:10 +02:00
sched/topology: Fix sched_numa_find_nth_cpu() in non-NUMA case
When CONFIG_NUMA is enabled, sched_numa_find_nth_cpu() searches for a
CPU in sched_domains_numa_masks. The masks includes only online CPUs,
so effectively offline CPUs are skipped.
When CONFIG_NUMA is disabled, the fallback function should be consistent.
Fixes: cd7f55359c90 ("sched: add sched_numa_find_nth_cpu()")
Signed-off-by: Yury Norov <yury.norov@gmail.com>
Signed-off-by: Ingo Molnar <mingo@kernel.org>
Cc: Mel Gorman <mgorman@suse.de>
Link: https://lore.kernel.org/r/20230819141239.287290-5-yury.norov@gmail.com
---
include/linux/topology.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/include/linux/topology.h b/include/linux/topology.h
index fea3237..52f5850 100644
--- a/include/linux/topology.h
+++ b/include/linux/topology.h
@@ -251,7 +251,7 @@ extern const struct cpumask *sched_numa_hop_mask(unsigned int node, unsigned int
#else
static __always_inline int sched_numa_find_nth_cpu(const struct cpumask *cpus, int cpu, int node)
{
- return cpumask_nth(cpu, cpus);
+ return cpumask_nth_and(cpu, cpus, cpu_online_mask);
}
static inline const struct cpumask *
next prev parent reply other threads:[~2023-09-15 12:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-19 14:12 [PATCH v2 0/6] sched fixes Yury Norov
2023-08-19 14:12 ` [PATCH v2 1/6] numa: generalize numa_map_to_online_node() Yury Norov
2023-09-15 12:03 ` [tip: sched/core] numa: Generalize numa_map_to_online_node() tip-bot2 for Yury Norov
2023-08-19 14:12 ` [PATCH v2 2/6] sched/fair: fix opencoded numa_nearest_node() Yury Norov
2023-09-15 12:03 ` [tip: sched/core] sched/fair: Fix open-coded numa_nearest_node() tip-bot2 for Yury Norov
2023-08-19 14:12 ` [PATCH v2 3/6] sched: fix sched_numa_find_nth_cpu() in CPU-less case Yury Norov
2023-09-15 12:03 ` [tip: sched/core] sched/topology: Fix " tip-bot2 for Yury Norov
2023-08-19 14:12 ` [PATCH v2 4/6] sched: fix sched_numa_find_nth_cpu() in non-NUMA case Yury Norov
2023-09-15 12:03 ` tip-bot2 for Yury Norov [this message]
2023-08-19 14:12 ` [PATCH v2 5/6] sched: handle NUMA_NO_NODE in sched_numa_find_nth_cpu() Yury Norov
2023-09-15 12:03 ` [tip: sched/core] sched/topology: Handle " tip-bot2 for Yury Norov
2023-08-19 14:12 ` [PATCH v2 6/6] sched: fix sched_numa_find_nth_cpu() comment Yury Norov
2023-09-15 12:03 ` [tip: sched/core] sched/topology: Fix " tip-bot2 for Yury Norov
2023-08-25 11:31 ` [PATCH v2 0/6] sched fixes Yury Norov
2023-09-13 0:01 ` Yury Norov
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=169477940797.27769.5804988700503210268.tip-bot2@tip-bot2 \
--to=tip-bot2@linutronix.de \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tip-commits@vger.kernel.org \
--cc=mgorman@suse.de \
--cc=mingo@kernel.org \
--cc=x86@kernel.org \
--cc=yury.norov@gmail.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®