linux-kernel - Re: [RFC PATCH v2] Add ARM cpu topology definition

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <BANLkTikQt8dgikHUM5NfYLjWwHgwLbeQrg@mail.gmail.com>
Date:	Wed, 22 Jun 2011 15:39:39 +0300
From:	Amit Kucheria <amit.kucheria@...aro.org>
To:	Vincent Guittot <vincent.guittot@...aro.org>
Cc:	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	linaro-dev@...ts.linaro.org, patches@...aro.org
Subject: Re: [RFC PATCH v2] Add ARM cpu topology definition

On Wed, Jun 22, 2011 at 3:20 PM, Vincent Guittot
<vincent.guittot@...aro.org> wrote:
> On 22 June 2011 12:14, Amit Kucheria <amit.kucheria@...aro.org> wrote:
>>> +
>>> +#define topology_physical_package_id(cpu)    (cpu_topology[cpu].socket_id)
>>> +#define topology_core_id(cpu)                (cpu_topology[cpu].core_id)
>>> +#define topology_core_cpumask(cpu)   (&(cpu_topology[cpu].core_sibling))
>>> +#define topology_thread_cpumask(cpu) (&(cpu_topology[cpu].thread_sibling))
>>
>> These #defines are not used anywhere.
>
> They are used in topology.c driver and sched.c
>
>>
>>> +#define mc_capable() (cpu_topology[0].socket_id != -1)
>>> +#define smt_capable()        (cpu_topology[0].thread_id != -1)
>>
>> Neither are these.
>
> They are used in sched.c
>

Ahh, sorry for the noise. Documentation/cputopology.txt is most illuminating.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/