From: Arnd Bergmann <arnd@kernel.org>
To: Siddharth Chintamaneni <sidchintamaneni@gmail.com>
Cc: Arnd Bergmann <arnd@arndb.de>, Fuad Tabba <fuad.tabba@linux.dev>,
Marc Zyngier <maz@kernel.org>, Oliver Upton <oupton@kernel.org>,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Suzuki K Poulose <suzuki.poulose@arm.com>,
Joey Gouly <joey.gouly@arm.com>,
Zenghui Yu <yuzenghui@huawei.com>,
Steffen Eiden <seiden@linux.ibm.com>,
Yicong Yang <yangyicong@hisilicon.com>,
Zhou Wang <wangzhou1@hisilicon.com>,
Navneet Singh <navneetsingh@microsoft.com>,
apais@microsoft.com, hargar@linux.microsoft.com,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] st64bv0 support in iommu-sva
Date: Tue, 17 Nov 2026 23:22:22 +0100 [thread overview]
Message-ID: <20261117222224.1465328-1-arnd@kernel.org> (raw)
From: Arnd Bergmann <arnd@arndb.de>
Hi Siddharth,
Here is a what I came up with for enabling ACCDATA in arm64 Linux,
similar to the earlier patch and rebased on current linux-next.
I hope this works for you, please let me know how it goes.
Arnd
Arnd Bergmann (2):
arm64: add HWCAP3_LS64_ACCDATA
arm64: dynamically enable st64bv0 for SVA
Documentation/arch/arm64/elf_hwcaps.rst | 7 ++++
arch/arm64/include/asm/cpufeature.h | 5 +++
arch/arm64/include/asm/exception.h | 1 +
arch/arm64/include/asm/mmu_context.h | 17 ++++++++
arch/arm64/include/uapi/asm/hwcap.h | 1 +
arch/arm64/kernel/cpufeature.c | 1 +
arch/arm64/kernel/cpuinfo.c | 1 +
arch/arm64/kernel/entry-common.c | 11 ++++++
arch/arm64/kernel/traps.c | 52 +++++++++++++++++++++++++
arch/arm64/tools/sysreg | 5 +++
10 files changed, 101 insertions(+)
--
2.53.0
Cc: Siddharth Chintamaneni <sidchintamaneni@gmail.com>
Cc: Fuad Tabba <fuad.tabba@linux.dev>
Cc: Marc Zyngier <maz@kernel.org>
Cc: Oliver Upton <oupton@kernel.org>,
Cc: Catalin Marinas <catalin.marinas@arm.com>,
Cc: Will Deacon <will@kernel.org>,
Cc: Mark Rutland <mark.rutland@arm.com>,
Cc: Suzuki K Poulose <suzuki.poulose@arm.com>,
Cc: Joey Gouly <joey.gouly@arm.com>,
Cc: Zenghui Yu <yuzenghui@huawei.com>,
Cc: Steffen Eiden <seiden@linux.ibm.com>,
Cc: Yicong Yang <yangyicong@hisilicon.com>,
Cc: Zhou Wang <wangzhou1@hisilicon.com>,
Cc: Navneet Singh <navneetsingh@microsoft.com>,
Cc: apais@microsoft.com, rlmenge@gmail.com,
Cc: hargar@linux.microsoft.com, kvmarm@lists.linux.dev,
Cc: linux-arm-kernel@lists.infradead.org, kvm@vger.kernel.org,
Cc: linux-kernel@vger.kernel.org,
next reply other threads:[~2026-11-17 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-17 22:22 Arnd Bergmann [this message]
2026-11-17 22:22 ` [PATCH 1/2] arm64: add HWCAP3_LS64_ACCDATA Arnd Bergmann
2026-11-17 22:22 ` [PATCH 2/2] arm64: dynamically enable st64bv0 for SVA Arnd Bergmann
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=20261117222224.1465328-1-arnd@kernel.org \
--to=arnd@kernel.org \
--cc=apais@microsoft.com \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=fuad.tabba@linux.dev \
--cc=hargar@linux.microsoft.com \
--cc=joey.gouly@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=navneetsingh@microsoft.com \
--cc=oupton@kernel.org \
--cc=seiden@linux.ibm.com \
--cc=sidchintamaneni@gmail.com \
--cc=suzuki.poulose@arm.com \
--cc=wangzhou1@hisilicon.com \
--cc=will@kernel.org \
--cc=yangyicong@hisilicon.com \
--cc=yuzenghui@huawei.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