linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Heiko Carstens <heiko.carstens@de.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: Suravee Suthikulpanit <suravee.suthikulpanit@amd.com>,
	Ingo Molnar <mingo@kernel.org>,
	Andre Wild <wild@linux.vnet.ibm.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [bisected] 051f3ca02e46 "Introduce NUMA identity node sched domain" breaks fake NUMA on s390
Date: Mon, 14 May 2018 12:30:13 +0200	[thread overview]
Message-ID: <20180514103013.GA3603@osiris> (raw)
In-Reply-To: <20180514093909.GO12217@hirez.programming.kicks-ass.net>

On Mon, May 14, 2018 at 11:39:09AM +0200, Peter Zijlstra wrote:
> On Sat, May 12, 2018 at 12:02:33PM +0200, Heiko Carstens wrote:
> > Hello,
> > 
> > Andre Wild reported that fake NUMA doesn't work on s390 anymore. Doesn't
> > work means it crashed for Andre, or it is in an endless loop within
> > init_sched_groups_capacity() for me (sg != sd->groups is always true).
> > 
> > I could reproduce this with a very simple setup with only two nodes, where
> > each node has only one CPU. This allowed me to bisect it down to commit
> > 051f3ca02e46 ("sched/topology: Introduce NUMA identity node sched domain").
> > 
> > With that commit reverted the system comes up again and the scheduling
> > domains look like this:
> > 
> > [    0.148592] smp: Bringing up secondary CPUs ...
> > [    0.148984] smp: Brought up 2 nodes, 2 CPUs
> > [    0.149097] CPU0 attaching sched-domain(s):
> > [    0.149099]  domain-0: span=0-1 level=NUMA
> > [    0.149101]   groups: 0:{ span=0 }, 1:{ span=1 }
> > [    0.149106] CPU1 attaching sched-domain(s):
> > [    0.149107]  domain-0: span=0-1 level=NUMA
> > [    0.149108]   groups: 1:{ span=1 }, 0:{ span=0 }
> > [    0.149111] span: 0-1 (max cpu_capacity = 1024)
> > 
> > Any idea what's going wrong?
> 
> Not yet; still trying to decipher your fake nume implementation.
> 
> But meanwhile; could you provide me with:
> 
> $ cat /sys/devices/system/node/node*/distance
> $ cat /sys/devices/system/node/node*/cpulist

Yes, of course:

$ cat /sys/devices/system/node/node0/distance
0 10
$ cat /sys/devices/system/node/node1/distance
10 0

$ cat /sys/devices/system/node/node0/cpulist
0
$ cat /sys/devices/system/node/node1/cpulist
1

      reply	other threads:[~2018-05-14 10:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-12 10:02 [bisected] 051f3ca02e46 "Introduce NUMA identity node sched domain" breaks fake NUMA on s390 Heiko Carstens
2018-05-14  9:39 ` Peter Zijlstra
2018-05-14 10:30   ` Heiko Carstens [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=20180514103013.GA3603@osiris \
    --to=heiko.carstens@de.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@kernel.org \
    --cc=peterz@infradead.org \
    --cc=suravee.suthikulpanit@amd.com \
    --cc=wild@linux.vnet.ibm.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;
as well as URLs for NNTP newsgroup(s).