From: Peter Zijlstra <peterz@infradead.org>
To: Lauro Venancio <lvenanci@redhat.com>
Cc: lwang@redhat.com, riel@redhat.com, Mike Galbraith <efault@gmx.de>,
Thomas Gleixner <tglx@linutronix.de>,
Ingo Molnar <mingo@kernel.org>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] sched/topology: the group balance cpu must be a cpu where the group is installed
Date: Tue, 25 Apr 2017 00:15:27 +0200 [thread overview]
Message-ID: <20170424221527.jf3gjh3qaz4eqtbp@hirez.programming.kicks-ass.net> (raw)
In-Reply-To: <5c03e2ca-e67a-f3e0-2a93-c91ba0f11973@redhat.com>
On Mon, Apr 24, 2017 at 12:11:59PM -0300, Lauro Venancio wrote:
> On 04/24/2017 10:03 AM, Peter Zijlstra wrote:
> > On Thu, Apr 20, 2017 at 04:51:43PM -0300, Lauro Ramos Venancio wrote:
> >
> >> diff --git a/kernel/sched/topology.c b/kernel/sched/topology.c
> >> index e77c93a..694e799 100644
> >> --- a/kernel/sched/topology.c
> >> +++ b/kernel/sched/topology.c
> >> @@ -505,7 +507,11 @@ static void build_group_mask(struct sched_domain *sd, struct sched_group *sg)
> >>
> >> for_each_cpu(i, sg_span) {
> >> sibling = *per_cpu_ptr(sdd->sd, i);
> >> - if (!cpumask_test_cpu(i, sched_domain_span(sibling)))
> >> +
> >> + if (!sibling->groups)
> >> + continue;
> > How can this happen?
> This happens on machines with asymmetric topologies. For more details see:
> https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=c1174876874dcf8986806e4dad3d7d07af20b439
Ah, ok. I'll put a comment with.
next prev parent reply other threads:[~2017-04-24 22:15 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-20 19:51 [PATCH 0/4] sched/topology: fix overlap group capacity and balance cpu Lauro Ramos Venancio
2017-04-20 19:51 ` [PATCH 1/4] sched/topology: optimize build_group_mask() Lauro Ramos Venancio
2017-05-15 9:06 ` [tip:sched/core] sched/topology: Optimize build_group_mask() tip-bot for Lauro Ramos Venancio
2017-04-20 19:51 ` [PATCH 2/4] sched/topology: all instances of a sched group must use the same sched_group_capacity Lauro Ramos Venancio
2017-04-20 19:51 ` [PATCH 3/4] sched/topology: move comment about asymmetric node setups Lauro Ramos Venancio
2017-04-21 16:31 ` Peter Zijlstra
2017-05-15 9:06 ` [tip:sched/core] sched/topology: Move " tip-bot for Lauro Ramos Venancio
2017-04-20 19:51 ` [PATCH 4/4] sched/topology: the group balance cpu must be a cpu where the group is installed Lauro Ramos Venancio
2017-04-24 13:03 ` Peter Zijlstra
2017-04-24 14:19 ` Peter Zijlstra
2017-04-24 14:27 ` Peter Zijlstra
2017-04-24 15:19 ` Lauro Venancio
2017-04-24 22:19 ` Peter Zijlstra
2017-04-24 15:11 ` Lauro Venancio
2017-04-24 22:15 ` Peter Zijlstra [this message]
2017-04-25 12:17 ` Peter Zijlstra
2017-04-25 14:33 ` Lauro Venancio
2017-04-25 15:12 ` Peter Zijlstra
2017-04-25 15:22 ` Peter Zijlstra
2017-04-25 15:27 ` Peter Zijlstra
2017-04-25 15:39 ` Peter Zijlstra
2017-04-25 15:52 ` Peter Zijlstra
2017-04-25 15:56 ` Lauro Venancio
2017-04-25 16:26 ` Peter Zijlstra
2017-04-26 16:31 ` [PATCH 0/4] sched/topology: fix overlap group capacity and balance cpu Peter Zijlstra
2017-04-26 17:59 ` Lauro Venancio
2017-04-26 22:43 ` Peter Zijlstra
2017-04-28 10:33 ` Peter Zijlstra
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=20170424221527.jf3gjh3qaz4eqtbp@hirez.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=efault@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lvenanci@redhat.com \
--cc=lwang@redhat.com \
--cc=mingo@kernel.org \
--cc=riel@redhat.com \
--cc=tglx@linutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).