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  PHC 
Open Source and information security mailing list archives
 
Hash Suite for Android: free password hash cracker in your pocket
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date:   Wed, 30 Nov 2016 11:30:08 +0000
From:   Suzuki K Poulose <Suzuki.Poulose@....com>
To:     Siddhesh Poyarekar <sid@...erved-bit.com>,
        <linux-arm-kernel@...ts.infradead.org>
CC:     <linux-kernel@...r.kernel.org>, <catalin.marinas@....com>,
        <dave.martin@....com>, <aph@...hat.com>, <will.deacon@....com>,
        <ryan.arnold@...aro.org>, <adhemerval.zanella@...aro.org>,
        <mark.rutland@....com>, <marc.zyngier@....com>
Subject: Re: [PATCH 9/9] arm64: Documentation - Expose CPU feature registers

On 30/11/16 11:14, Siddhesh Poyarekar wrote:
> On Thursday 24 November 2016 07:10 PM, Suzuki K Poulose wrote:
>> + d) CPU Identification :
>> +    MIDR_EL1 is exposed to help identify the processor. On a
>> +    heterogeneous system, this could be racy (just like getcpu()). The
>> +    process could be migrated to another CPU by the time it uses the
>> +    register value, unless the CPU affinity is set. Hence, there is no
>> +    guarantee that the value reflects the processor that it is
>> +    currently executing on. The REVIDR is not exposed due to this
>> +    constraint, as REVIDR makes sense only in conjunction with the
>> +    MIDR. Alternately, MIDR_EL1 and REVIDR_EL1 are exposed via sysfs
>> +    at:
>> +
>> +    /sys/devices/system/cpu/cpu$ID/regs/identification/
>> +                                                  \- midr
>> +                                                  \- revidr
>> +
>
> This doesn't seem to be implemented in this patchset.

This is already available upstream.

Thanks
Suzuki

IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.

Powered by blists - more mailing lists