From: Catalin Marinas <catalin.marinas@arm.com>
To: Mark Brown <broonie@kernel.org>
Cc: Will Deacon <will.deacon@arm.com>, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 1/2] arm64: Expose ARMv8.5 CondM capability to userspace
Date: Tue, 25 Jun 2019 14:26:15 +0100 [thread overview]
Message-ID: <20190625132614.GA32618@arrakis.emea.arm.com> (raw)
In-Reply-To: <20190618181055.31576-1-broonie@kernel.org>
On Tue, Jun 18, 2019 at 07:10:54PM +0100, Mark Brown wrote:
> ARMv8.5 adds new instructions XAFLAG and AXFLAG to translate the
> representation of the results of floating point comparisons between the
> native ARM format and an alternative format used by some software. Add
> a hwcap allowing userspace to determine if they are present, since we
> referred to earlier CondM extensions as FLAGM call these extensions
> FLAGM2.
>
> Signed-off-by: Mark Brown <broonie@kernel.org>
> Acked-by: Will Deacon <will.deacon@arm.com>
> ---
> Documentation/arm64/elf_hwcaps.rst | 4 ++++
> arch/arm64/include/asm/hwcap.h | 1 +
> arch/arm64/include/uapi/asm/hwcap.h | 1 +
> arch/arm64/kernel/cpufeature.c | 1 +
> arch/arm64/kernel/cpuinfo.c | 1 +
> 5 files changed, 8 insertions(+)
I queued both patches but changed them to apply to the elf_hwcap.txt
file instead of .rst (arm64 for-next/core is based on 5.2-rc3).
Thanks.
--
Catalin
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next parent reply other threads:[~2019-06-25 13:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20190618181055.31576-1-broonie@kernel.org>
2019-06-25 13:26 ` Catalin Marinas [this message]
2019-06-17 11:26 [PATCH 1/2] arm64: Expose ARMv8.5 CondM capability to userspace Mark Brown
2019-06-18 16:51 ` 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=20190625132614.GA32618@arrakis.emea.arm.com \
--to=catalin.marinas@arm.com \
--cc=broonie@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=will.deacon@arm.com \
/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).