From: Szabolcs Nagy <szabolcs.nagy@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v4 1/3] arm64/hwcap: Document allocation of upper bits of AT_HWCAP
Date: Thu, 7 Jul 2022 10:00:53 +0100 [thread overview]
Message-ID: <YsagxXSfCQXKF+yq@arm.com> (raw)
In-Reply-To: <20220706175256.847703-2-broonie@kernel.org>
The 07/06/2022 18:52, Mark Brown wrote:
> The top two bits of AT_HWCAP are reserved for use by glibc and the rest of
> the top 32 bits are being kept unallocated for potential use by glibc.
> Document this in the header.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> ---
> arch/arm64/include/uapi/asm/hwcap.h | 3 +++
> 1 file changed, 3 insertions(+)
>
> diff --git a/arch/arm64/include/uapi/asm/hwcap.h b/arch/arm64/include/uapi/asm/hwcap.h
> index 4bb2cc8ac446..cc2ccd0a9edf 100644
> --- a/arch/arm64/include/uapi/asm/hwcap.h
> +++ b/arch/arm64/include/uapi/asm/hwcap.h
> @@ -19,6 +19,9 @@
>
> /*
> * HWCAP flags - for AT_HWCAP
> + *
> + * Bits 60 and 61 are reserved for use by libc.
should be 62 and 63
> + * Bits 32-59 are unallocated for potential use by libc.
32-61
> */
> #define HWCAP_FP (1 << 0)
> #define HWCAP_ASIMD (1 << 1)
> --
> 2.30.2
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2022-07-07 9:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-06 17:52 [PATCH v4 0/3] arm64: Start allocating upper bits of AT_HWCAP2 Mark Brown
2022-07-06 17:52 ` [PATCH v4 1/3] arm64/hwcap: Document allocation of upper bits of AT_HWCAP Mark Brown
2022-07-07 9:00 ` Szabolcs Nagy [this message]
2022-07-06 17:52 ` [PATCH v4 2/3] arm64/cpufeature: Store elf_hwcaps as a bitmap rather than unsigned long Mark Brown
2022-07-06 17:52 ` [PATCH v4 3/3] arm64/hwcap: Support FEAT_EBF16 Mark Brown
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YsagxXSfCQXKF+yq@arm.com \
--to=szabolcs.nagy@arm.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=suzuki.poulose@arm.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.