[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <cf4fdb30-6f2e-ca3e-fbc0-b48f6949508d@gmail.com>
Date: Sat, 15 Apr 2023 09:24:28 +0700
From: Bagas Sanjaya <bagasdotme@...il.com>
To: K Prateek Nayak <kprateek.nayak@....com>,
linux-kernel@...r.kernel.org
Cc: tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
dave.hansen@...ux.intel.com, hpa@...or.com, corbet@....net,
jgross@...e.com, andrew.cooper3@...rix.com, peterz@...radead.org,
Jason@...c4.com, thomas.lendacky@....com, puwen@...on.cn,
x86@...nel.org, linux-doc@...r.kernel.org, oleksandr@...alenko.name
Subject: Re: [PATCH v2.1 2/2] x86/Documentation: Add documentation about
cluster
On 4/14/23 10:17, K Prateek Nayak wrote:
> + - cluster_id:
> +
> + A per-CPU variable containing:
> +
> + - Upper bits extracted from the APIC ID. CPUs which have the same value
> + in these bits share an L2 and have the same cluster_id.
> +
> + CPUs for which cluster information is unavailable will show 65535
> + (BAD_APICID) as the cluster_id.
"... return cluster_id of 65535 (BAD_APICID)."
> The number of online threads is also printed in /proc/cpuinfo "siblings."
>
> + - topology_cluster_cpumask():
> +
> + The cpumask contains all online threads in the cluster to which a thread
> + belongs.
> +
Looks OK.
> The physical package ID to which a thread belongs.
>
> + - topology_cluster_id();
> +
> + The ID of the cluster to which a thread belongs.
> +
Looks OK.
Thanks.
--
An old man doll... just what I always wanted! - Clara
Powered by blists - more mailing lists