From: catalin.marinas@arm.com (Catalin Marinas)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v4 7/9] arm64: cpufeature: Track user visible fields
Date: Tue, 10 Jan 2017 14:24:27 +0000 [thread overview]
Message-ID: <20170110142427.GA23051@e104818-lin.cambridge.arm.com> (raw)
In-Reply-To: <1483982912-27215-8-git-send-email-suzuki.poulose@arm.com>
On Mon, Jan 09, 2017 at 05:28:30PM +0000, Suzuki K. Poulose wrote:
> Changes since V3:
> - Mark ID_AA64ISAR0_EL1:RDM visible
[...]
> static const struct arm64_ftr_bits ftr_id_aa64isar0[] = {
> - ARM64_FTR_BITS(FTR_STRICT, FTR_EXACT, ID_AA64ISAR0_RDM_SHIFT, 4, 0),
> - ARM64_FTR_BITS(FTR_STRICT, FTR_LOWER_SAFE, ID_AA64ISAR0_ATOMICS_SHIFT, 4, 0),
> - ARM64_FTR_BITS(FTR_STRICT, FTR_LOWER_SAFE, ID_AA64ISAR0_CRC32_SHIFT, 4, 0),
> - ARM64_FTR_BITS(FTR_STRICT, FTR_LOWER_SAFE, ID_AA64ISAR0_SHA2_SHIFT, 4, 0),
> - ARM64_FTR_BITS(FTR_STRICT, FTR_LOWER_SAFE, ID_AA64ISAR0_SHA1_SHIFT, 4, 0),
> - ARM64_FTR_BITS(FTR_STRICT, FTR_LOWER_SAFE, ID_AA64ISAR0_AES_SHIFT, 4, 0),
> + ARM64_FTR_BITS(FTR_VISIBLE, FTR_STRICT, FTR_EXACT, ID_AA64ISAR0_RDM_SHIFT, 4, 0),
As I said in an earlier reply, I'd like the RDM exposing to come
together with a patch presenting the corresponding HWCAP bit. But it's
fine by me if you add the HWCAP separately from this patch, in which
case my ack still stands.
--
Catalin
next prev parent reply other threads:[~2017-01-10 14:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-09 17:28 [PATCH v4 0/9] arm64: Expose CPUID registers via emulation Suzuki K Poulose
2017-01-09 17:28 ` [PATCH v4 1/9] arm64: cpufeature: treat unknown fields as RES0 Suzuki K Poulose
2017-01-09 17:28 ` [PATCH v4 2/9] arm64: cpufeature: remove explicit RAZ fields Suzuki K Poulose
2017-01-09 17:28 ` [PATCH v4 3/9] arm64: cpufeature: Cleanup feature bit tables Suzuki K Poulose
2017-01-09 17:28 ` [PATCH v4 4/9] arm64: cpufeature: Document the rules of safe value for features Suzuki K Poulose
2017-01-09 17:28 ` [PATCH v4 5/9] arm64: cpufeature: Define helpers for sys_reg id Suzuki K Poulose
2017-01-09 17:28 ` [PATCH v4 6/9] arm64: Add helper to decode register from instruction Suzuki K Poulose
2017-01-09 17:28 ` [PATCH v4 7/9] arm64: cpufeature: Track user visible fields Suzuki K Poulose
2017-01-10 14:24 ` Catalin Marinas [this message]
2017-01-10 14:25 ` Suzuki K Poulose
2017-01-09 17:28 ` [PATCH v4 8/9] arm64: cpufeature: Expose CPUID registers by emulation Suzuki K Poulose
2017-01-09 17:28 ` [PATCH v4 9/9] arm64: Documentation - Expose CPU feature registers Suzuki K Poulose
2017-01-10 17:15 ` [PATCH v4 0/9] arm64: Expose CPUID registers via emulation Will Deacon
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=20170110142427.GA23051@e104818-lin.cambridge.arm.com \
--to=catalin.marinas@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).