[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160510065133.GF3408@twins.programming.kicks-ass.net>
Date: Tue, 10 May 2016 08:51:33 +0200
From: Peter Zijlstra <peterz@...radead.org>
To: Thomas Gleixner <tglx@...utronix.de>
Cc: Josef Bacik <jbacik@...com>, LKML <linux-kernel@...r.kernel.org>,
kernel-team <Kernel-team@...com>, x86@...nel.org,
Kan Liang <kan.liang@...el.com>
Subject: Re: Regression introduced by cf6d445f68974d0b15a14cf6021be38a91f2b5d8
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.
Powered by blists - more mailing lists