linux-kernel - Re: [RFC] 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] [thread-next>] [day] [month] [year] [list]

Message-ID: <4E0100BF.6080500@codeaurora.org>
Date:	Tue, 21 Jun 2011 13:36:15 -0700
From:	Stephen Boyd <sboyd@...eaurora.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
Subject: Re: [RFC] Add Arm cpu topology definition

On 06/16/2011 11:54 PM, Vincent Guittot wrote:
> On 16 June 2011 21:40, Stephen Boyd <sboyd@...eaurora.org> wrote:
>> The ARM ARM says these fields are IMPLEMENTATION DEFINED meaning that
>> different vendors may attribute different meaning to these fields if
>> they wish. Does that mean this should be a platform_*() function?
>>
> The ARM ARM also provides a recommended use of the fields of this
> register and the TRM of each Cortex adds some details. On the cortex
> A9, each platform can only set the value of the Cluster ID with the
> CLUSTERID pins. I have tried to consolidate the value of MPIDR  across
> several platforms and they all match with the description.
>
> Have you got an example of a MPIDR register which doesn't match with
> the implementation ?

Not that I know of. I'm more concerned with how the ARM ARM has two
recommended usages for these fields depending on virtualization or not.
I suppose we can handle that issue when it arises (or does your
implementation already handle that?)

-- 
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum.

--
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/