[RFC PATCH 01/10] arm64: feature registers: Documentation
Suzuki K. Poulose
Suzuki.Poulose at arm.com
Tue Aug 11 01:41:01 PDT 2015
On 10/08/15 19:19, Andrew Haley wrote:
> On 08/10/2015 06:36 PM, Suzuki K. Poulose wrote:
>> On 10/08/15 17:06, Catalin Marinas wrote:
>>> Hi Suzuki,
>>> On Fri, Jul 24, 2015 at 10:43:47AM +0100, Suzuki K. Poulose wrote:
>>>> From: "Suzuki K. Poulose" <suzuki.poulose at arm.com>
>>>> Documentation of the infrastructure
>>>> Signed-off-by: Suzuki K. Poulose <suzuki.poulose at arm.com>
>>> The implementation looks fine but I think the main discussion will be
>>> around the goal of this feature and the ABI that it introduces. So I'll
>>> just write my thoughts on this patch (I could as well have replied to
>>> the cover letter).
>>> Another question: who's going to use this feature? I know people asked
>>> in private but I'd like to have some public statements.
>> Right, I am hoping that folks from glibc / JIT / GCC will respond to
>> this thread.
> We certainly need it for OpenJDK. We need to know the manufacturer,
> part number, revision id, etc. We already have workarounds in
> OpenJDK for various bugs, and we also can generate better code if we
> know the exact part.
> I note that the REVIDR is not in this patch. That seems odd, because
> it can be used to identify minor revisions.
The REVIDR has to be used in conjunction with the MIDR to make real sense.
We cannot guarantee that the REVIDR that we read (would) belong to the CPU
where MIDR would have been read (unless the process is pinned) and hence the
user may not be able to make any use of the information. Steve has a patch 
to expose the MIDR,REVIDR info via sysfs.
More information about the linux-arm-kernel