All of lore.kernel.org
 help / color / mirror / Atom feed
From: Amit Daniel Kachhap <amit.kachhap@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: Catalin Marinas <catalin.marinas@arm.com>,
	Will Deacon <will@kernel.org>,
	Linus Walleij <linus.walleij@linaro.org>,
	Amit Daniel Kachhap <amit.kachhap@arm.com>
Subject: [PATCH v2 0/7] arm64: Expose compat Armv8 AArch32 features
Date: Wed, 11 Jan 2023 11:06:59 +0530	[thread overview]
Message-ID: <20230111053706.13994-1-amit.kachhap@arm.com> (raw)

Hi All,

This series advertises the Armv8 AArch32 features in arm64 kernel in
compat mode. A similar series adding such features (fphp, asimdhp, dp,
fhm, bf16, i8mm, sb and ssbs) in arm kernel was posted and merged
earlier.

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 different hwcaps added are visible in
/proc/cpuinfo in PER_LINUX32 personality mode.

The series is based on Linux v6.2-rc3.

Changes in V2:
* Dropped the patch "arm64: cpufeature: Fix the visibility of compat hwcaps"
  as it is merged.
* Rebased to 6.2-rc3.
* Few commit log modifications.

Thanks,
Amit Daniel

Amit Daniel Kachhap (7):
  arm64: Add compat hwcap FPHP and ASIMDHP
  arm64: Add compat hwcap ASIMDDP
  arm64: Add compat hwcap ASIMDFHM
  arm64: Add compat hwcap ASIMDBF16
  arm64: Add compat hwcap I8MM
  arm64: Add compat hwcap SB
  arm64: Add compat hwcap SSBS

 arch/arm64/include/asm/hwcap.h |  8 ++++++++
 arch/arm64/kernel/cpufeature.c | 24 ++++++++++++++++--------
 arch/arm64/kernel/cpuinfo.c    |  8 ++++++++
 3 files changed, 32 insertions(+), 8 deletions(-)

-- 
2.17.1


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

             reply	other threads:[~2023-01-11  5:38 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-11  5:36 Amit Daniel Kachhap [this message]
2023-01-11  5:37 ` [PATCH v2 1/7] arm64: Add compat hwcap FPHP and ASIMDHP Amit Daniel Kachhap
2023-01-11 20:07   ` Mark Brown
2023-01-11  5:37 ` [PATCH v2 2/7] arm64: Add compat hwcap ASIMDDP Amit Daniel Kachhap
2023-01-11 20:11   ` Mark Brown
2023-01-11  5:37 ` [PATCH v2 3/7] arm64: Add compat hwcap ASIMDFHM Amit Daniel Kachhap
2023-01-19 15:02   ` Mark Brown
2023-01-11  5:37 ` [PATCH v2 4/7] arm64: Add compat hwcap ASIMDBF16 Amit Daniel Kachhap
2023-01-19 15:03   ` Mark Brown
2023-01-11  5:37 ` [PATCH v2 5/7] arm64: Add compat hwcap I8MM Amit Daniel Kachhap
2023-01-19 15:04   ` Mark Brown
2023-01-11  5:37 ` [PATCH v2 6/7] arm64: Add compat hwcap SB Amit Daniel Kachhap
2023-01-19 15:06   ` Mark Brown
2023-01-11  5:37 ` [PATCH v2 7/7] arm64: Add compat hwcap SSBS Amit Daniel Kachhap
2023-01-19 15:06   ` Mark Brown
2023-01-11 13:49 ` [PATCH v2 0/7] arm64: Expose compat Armv8 AArch32 features Mark Brown
2023-01-12  5:12   ` Amit Daniel Kachhap
2023-01-20 16:58 ` 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=20230111053706.13994-1-amit.kachhap@arm.com \
    --to=amit.kachhap@arm.com \
    --cc=catalin.marinas@arm.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=will@kernel.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.