From: Peter Zijlstra <peterz@infradead.org>
To: Thomas Gleixner <tglx@linutronix.de>
Cc: Josef Bacik <jbacik@fb.com>, LKML <linux-kernel@vger.kernel.org>,
kernel-team <Kernel-team@fb.com>,
x86@kernel.org, Kan Liang <kan.liang@intel.com>
Subject: Re: Regression introduced by cf6d445f68974d0b15a14cf6021be38a91f2b5d8
Date: Tue, 10 May 2016 08:51:33 +0200 [thread overview]
Message-ID: <20160510065133.GF3408@twins.programming.kicks-ass.net> (raw)
In-Reply-To: <alpine.DEB.2.11.1605092132090.3540@nanos>
On Mon, May 09, 2016 at 09:48:18PM +0200, Thomas Gleixner wrote:
> So that explains the wreckage you are seing. We have two options to deal with
> this:
>
> 1) Make intel_num_cpu_cores() a NOOP for SMP=n, so x86_max_cores = 1
This I think; because:
>
> 2) Make detect_extended_topology() functional for SMP=n, so the real number of
> cores is detected
UP has no business 'knowing' anything about cores/threads and general
topology stuff.
next prev parent reply other threads:[~2016-05-10 6:51 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-09 18:39 Regression introduced by cf6d445f68974d0b15a14cf6021be38a91f2b5d8 Josef Bacik
2016-05-09 19:48 ` Thomas Gleixner
2016-05-09 20:55 ` Liang, Kan
2016-05-10 6:51 ` Peter Zijlstra [this message]
2016-05-10 7:33 ` [tip:x86/urgent] x86/topology: Set x86_max_cores to 1 for CONFIG_SMP=n tip-bot for Thomas Gleixner
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=20160510065133.GF3408@twins.programming.kicks-ass.net \
--to=peterz@infradead.org \
--cc=Kernel-team@fb.com \
--cc=jbacik@fb.com \
--cc=kan.liang@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=tglx@linutronix.de \
--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;
as well as URLs for NNTP newsgroup(s).