linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: "Russell King (Oracle)" <linux@armlinux.org.uk>
To: Amit Daniel Kachhap <amit.kachhap@arm.com>
Cc: patches@armlinux.org.uk, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/8] ARM: Expose Armv8 AArch32 features via hwcap
Date: Mon, 21 Nov 2022 19:04:41 +0000	[thread overview]
Message-ID: <Y3vLyUuTHGfbY8A5@shell.armlinux.org.uk> (raw)
In-Reply-To: <20221026055001.12986-1-amit.kachhap@arm.com>

On Wed, Oct 26, 2022 at 11:19:53AM +0530, Amit Daniel Kachhap wrote:
> Hi All,
> 
> This series advertise availability of Armv8 features present in AArch32
> state. These features are mostly Advanced SIMD(fphp, asimdhp, dp,
> fhm, bf16, i8mm) and few others(sb ssbs). These features are already exposed
> to user in arm64 kernel. A similar series advertising the features in
> arm64 kernel in compat mode will be sent separately.
> 
> Some other remaining features(SPECRES,  ETS, nTLBPA, CSV3, LSMAOC) are not
> advertised in arm64 kernel so left here also.
> 
> The entire series is divided feature wise as present in Armv8 manual.
> The details of these features can be found in Armv8 architecture
> reference manual available from
> https://developer.arm.com/documentation/ddi0487/gb/?lang=en
> 
> All the changes have been tested on Arm FVP Base Revc model after adding
> necessary model parameters.
> 
> The series is based on Linux 6.1-rc1.

Hi Amit,

Please could you list which CPUs support running aarch32 _and_ support
these features?

Thanks!

-- 
RMK's Patch system: https://www.armlinux.org.uk/developer/patches/
FTTP is here! 40Mbps down 10Mbps up. Decent connectivity at last!

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2022-11-21 19:07 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-26  5:49 [PATCH 0/8] ARM: Expose Armv8 AArch32 features via hwcap Amit Daniel Kachhap
2022-10-26  5:49 ` [PATCH 1/8] ARM: Define Armv8 registers in AArch32 state Amit Daniel Kachhap
2022-10-26  5:49 ` [PATCH 2/8] ARM: vfp: Add hwcap FPHP and ASIMDHP for FEAT_FP16 Amit Daniel Kachhap
2022-10-26  5:49 ` [PATCH 3/8] ARM: vfp: Add hwcap for FEAT_DotProd Amit Daniel Kachhap
2022-10-26  5:49 ` [PATCH 4/8] ARM: vfp: Add hwcap for FEAT_FHM Amit Daniel Kachhap
2022-10-26  5:49 ` [PATCH 5/8] ARM: vfp: Add hwcap for FEAT_AA32BF16 Amit Daniel Kachhap
2022-10-26  5:49 ` [PATCH 6/8] ARM: vfp: Add hwcap for FEAT_AA32I8MM Amit Daniel Kachhap
2022-10-26  5:50 ` [PATCH 7/8] ARM: Add hwcap for Speculation Barrier(SB) Amit Daniel Kachhap
2022-11-16 14:06   ` Linus Walleij
2022-11-17 10:19     ` Amit Daniel Kachhap
2022-11-17 11:14     ` Robin Murphy
2022-10-26  5:50 ` [PATCH 8/8] ARM: Add hwcap for Speculative Store Bypassing Safe Amit Daniel Kachhap
2022-11-16 13:51 ` [PATCH 0/8] ARM: Expose Armv8 AArch32 features via hwcap Linus Walleij
2022-11-17  6:19   ` Amit Kachhap
2022-11-21 19:04 ` Russell King (Oracle) [this message]
2022-11-22 12:24   ` Amit Daniel Kachhap

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=Y3vLyUuTHGfbY8A5@shell.armlinux.org.uk \
    --to=linux@armlinux.org.uk \
    --cc=amit.kachhap@arm.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=patches@armlinux.org.uk \
    /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).