From: will.deacon@arm.com (Will Deacon)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 2/2] arm64: Expose Arm v8.4 features
Date: Mon, 26 Feb 2018 18:05:21 +0000 [thread overview]
Message-ID: <20180226180521.GH26147@arm.com> (raw)
In-Reply-To: <20180207142106.10716-2-suzuki.poulose@arm.com>
On Wed, Feb 07, 2018 at 02:21:06PM +0000, Suzuki K Poulose wrote:
> Expose the new features introduced by Arm v8.4 extensions to
> Arm v8-A profile.
>
> These include :
>
> 1) Data indpendent timing of instructions. (DIT, exposed as HWCAP_DIT)
> 2) Unaligned atomic instructions and Single-copy atomicity of loads
> and stores. (AT, expose as HWCAP_USCAT)
> 3) LDAPR and STLR instructions with immediate offsets (extension to
> LRCPC, exposed as HWCAP_ILRCPC)
> 4) Flag manipulation instructions (TS, exposed as HWCAP_FLAGM).
Please resend this but continuing with the default of FTR_STRICT, as we
currently have. That way this can be merged while we work out what we want
to do there.
> While at it get rid of the RES0 entries in the cpu-feature-registers.txt
> documentation, as:
> 1) We care only about the user visible fields.
> 2) The field may not be up-to-date
> 3) We already explain the rules of the fields if it is not visible.
Please spin this part as a separate patch.
Will
next prev parent reply other threads:[~2018-02-26 18:05 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-07 14:21 [PATCH v2 1/2] arm64: Relax constraints on ID feature bits Suzuki K Poulose
2018-02-07 14:21 ` [PATCH v2 2/2] arm64: Expose Arm v8.4 features Suzuki K Poulose
2018-02-26 18:05 ` Will Deacon [this message]
2018-02-07 15:09 ` [PATCH v2 1/2] arm64: Relax constraints on ID feature bits Dave Martin
2018-02-07 15:10 ` Suzuki K Poulose
2018-02-26 18:05 ` Will Deacon
2018-03-07 15:11 ` Suzuki K Poulose
2018-03-08 17:11 ` Will Deacon
2018-03-09 10:06 ` Suzuki K Poulose
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=20180226180521.GH26147@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).