[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [RFC PATCH hurd] Add partial /proc/cpuinfo implementation
From: |
Diego Nieto Cid |
Subject: |
Re: [RFC PATCH hurd] Add partial /proc/cpuinfo implementation |
Date: |
Thu, 9 Jan 2025 15:12:00 +0000 |
Hi,
On Thu, Jan 09, 2025 at 11:51:27AM +0300, Sergey Bugaev wrote:
>
> "Implementer", "architecture", "variant", "part", "revision" come from
> midr/revidr [0], and "features" are hwcap names. These are privileged
> registers that only EL1 can read, but on AArch64 gnumach, their values
> are obtainable from userland using the aarch64_get_hwcaps RPC (see
> gnumach:aarch64/include/mach/aarch64/mach_aarch64.defs and
> gnumach:aarch64/include/mach/aarch64/mach_aarch64_types.h).
Looking at the types.h header, I see there are HWCAP2_* definitions for
bits above 32. Since hwcaps_t is an uint32_t and the defs file claims to
return two values (I assume the first for HWCAP_* and the second for
HWCAP2_*), I don't see how to get the higher bits of HWCAP2_*.
How does that work?
- [RFC PATCH hurd] Add partial /proc/cpuinfo implementation, dnietoc, 2025/01/07
- Re: [RFC PATCH hurd] Add partial /proc/cpuinfo implementation, Luca, 2025/01/08
- Re: [RFC PATCH hurd] Add partial /proc/cpuinfo implementation, Diego Nieto Cid, 2025/01/08
- Re: [RFC PATCH hurd] Add partial /proc/cpuinfo implementation, Luca, 2025/01/08
- Re: [RFC PATCH hurd] Add partial /proc/cpuinfo implementation, Sergey Bugaev, 2025/01/09
- Re: [RFC PATCH hurd] Add partial /proc/cpuinfo implementation,
Diego Nieto Cid <=
- Re: [RFC PATCH hurd] Add partial /proc/cpuinfo implementation, Jessica Clarke, 2025/01/09
- Re: [RFC PATCH hurd] Add partial /proc/cpuinfo implementation, Sergey Bugaev, 2025/01/09
- Re: [RFC PATCH hurd] Add partial /proc/cpuinfo implementation, Samuel Thibault, 2025/01/12
- Re: [RFC PATCH hurd] Add partial /proc/cpuinfo implementation, Sergey Bugaev, 2025/01/13