From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] arm64: Add support for Half precision floating point
Date: Tue, 26 Jan 2016 16:02:58 +0000 [thread overview]
Message-ID: <20160126160257.GB28238@arm.com> (raw)
In-Reply-To: <1453823566-26742-1-git-send-email-suzuki.poulose@arm.com>
Hi Suzuki,
On Tue, Jan 26, 2016 at 03:52:46PM +0000, Suzuki K Poulose wrote:
> ARMv8.2 extensions [1] include an optional feature, which supports
> half precision(16bit) floating point/asimd data processing
> instructions. This patch adds support for detecting and exposing
> the same to the userspace via HWCAPs
>
> [1] https://community.arm.com/groups/processors/blog/2016/01/05/armv8-a-architecture-evolution
>
> Signed-off-by: Suzuki K. Poulose <suzuki.poulose@arm.com>
> ---
> arch/arm64/include/uapi/asm/hwcap.h | 2 ++
> arch/arm64/kernel/cpufeature.c | 2 ++
> arch/arm64/kernel/cpuinfo.c | 2 ++
> 3 files changed, 6 insertions(+)
>
> diff --git a/arch/arm64/include/uapi/asm/hwcap.h b/arch/arm64/include/uapi/asm/hwcap.h
> index 361c8a8..a739287 100644
> --- a/arch/arm64/include/uapi/asm/hwcap.h
> +++ b/arch/arm64/include/uapi/asm/hwcap.h
> @@ -28,5 +28,7 @@
> #define HWCAP_SHA2 (1 << 6)
> #define HWCAP_CRC32 (1 << 7)
> #define HWCAP_ATOMICS (1 << 8)
> +#define HWCAP_FPHP (1 << 9)
> +#define HWCAP_ASIMDHP (1 << 10)
Where did we get to with the mrs trapping you proposed here?
http://lists.infradead.org/pipermail/linux-arm-kernel/2015-October/374609.html
At some point, we need to consider whether or not we want to continue
adding new HWCAPs or whether your suggestion above is actually useful
to userspace.
Did the libc guys get anywhere with a prototype? What do we need to do
to make progress with it?
Will
next prev parent reply other threads:[~2016-01-26 16:02 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-26 15:52 [PATCH] arm64: Add support for Half precision floating point Suzuki K Poulose
2016-01-26 16:02 ` Will Deacon [this message]
2016-01-26 16:11 ` Catalin Marinas
2016-01-28 16:00 ` Will Deacon
2016-02-16 11:48 ` Szabolcs Nagy
2016-02-16 11:53 ` Will Deacon
2016-02-16 12:57 ` Szabolcs Nagy
2016-01-26 16:21 ` Suzuki K. Poulose
2016-01-26 16:55 ` Siddhesh Poyarekar
2016-01-28 16:07 ` Will Deacon
2016-01-28 16:46 ` Siddhesh Poyarekar
2016-01-28 17:27 ` Catalin Marinas
2016-01-28 17:44 ` Siddhesh Poyarekar
2016-01-28 17:55 ` Suzuki K. Poulose
2016-01-28 16:51 ` Adhemerval Zanella
2016-02-02 17:31 ` Szabolcs Nagy
2016-02-02 18:12 ` Adhemerval Zanella
2016-02-02 18:25 ` Szabolcs Nagy
2016-02-02 18:28 ` Adhemerval Zanella
2016-02-26 15:37 ` Catalin Marinas
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=20160126160257.GB28238@arm.com \
--to=will.deacon@arm.com \
--cc=linux-arm-kernel@lists.infradead.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.