[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <2448f18f-2f3a-4158-89c4-91415bca9eb1@intel.com>
Date: Wed, 31 Jan 2024 15:47:08 -0800
From: Sohil Mehta <sohil.mehta@...el.com>
To: Thomas Gleixner <tglx@...utronix.de>, LKML <linux-kernel@...r.kernel.org>
CC: <x86@...nel.org>, Tom Lendacky <thomas.lendacky@....com>, Andrew Cooper
<andrew.cooper3@...rix.com>, Arjan van de Ven <arjan@...ux.intel.com>, "Huang
Rui" <ray.huang@....com>, Juergen Gross <jgross@...e.com>, Dimitri Sivanich
<dimitri.sivanich@....com>, K Prateek Nayak <kprateek.nayak@....com>, "Kan
Liang" <kan.liang@...ux.intel.com>, Zhang Rui <rui.zhang@...el.com>, "Paul E.
McKenney" <paulmck@...nel.org>, Feng Tang <feng.tang@...el.com>, "Andy
Shevchenko" <andy@...radead.org>, Michael Kelley <mhklinux@...look.com>,
"Peter Zijlstra (Intel)" <peterz@...radead.org>
Subject: Re: [patch v2 14/30] x86/cpu/topology: Rework possible CPU management
On 1/23/2024 5:11 AM, Thomas Gleixner wrote:
> + pr_info("Allowing %u present CPUs plus %u hotplug CPUs\n", assigned, disabled);
> + if (topo_info.nr_rejected_cpus)
> + pr_info("Rejected CPUs %u\n", topo_info.nr_rejected_cpus);
> +
I encountered the same issue that Micheal mentions in the other thread.
This is how the messages show up in a 40-cpu system with:
nr_cpus=2 (correct)
-------------------
CPU topo: Allowing 2 present CPUs plus 0 hotplug CPUs
CPU topo: Rejected CPUs 38
nr_cpus=1 (incorrect)
---------------------
CPU topo: Allowing 1 present CPUs plus 0 hotplug CPUs
CPU topo: Rejected CPUs 40
Sohil
Powered by blists - more mailing lists