From: Suzuki K Poulose <suzuki.poulose@arm.com>
To: linux-arm-kernel@lists.infradead.org
Cc: catalin.marinas@arm.com, will@kernel.org,
linux-kernel@vger.kernel.org, maz@kernel.org,
pavan.kondeti@oss.qualcomm.com, tabba@google.com,
aneesh.kumar@kernel.org, mark.rutland@arm.com,
sdonthineni@nvidia.com, steven.price@arm.com, gshan@redhat.com,
yuzenghui@huawei.com, kvmarm@lists.linux.dev,
Suzuki K Poulose <suzuki.poulose@arm.com>
Subject: [PATCH v17 0/1] arm64: mm: Handle Granule Protection Faults (GPFs)
Date: Mon, 7 Sep 2026 17:22:03 +0100 [thread overview]
Message-ID: <20260907162204.1479401-1-suzuki.poulose@arm.com> (raw)
This single patch teaches the arm64 fault handling code about Granule
Protection Faults, introduced by FEAT_RME. This was posted with KVM CCA
support series, but split from that, to allow for other users of GPF.
The immediate user is KVM CCA, where the host may fault if it accesses
granules that have been delegated for use by a Realm. However, the fault
handling itself is architectural and not KVM-specific. It should also be useful
for other FEAT_RME users where an access to secure memory or root memory can
result in a GPF.
GPFs during a page table walk are treated as kernel bugs, while non-page-walk
faults can be reported to userspace with SIGBUS. The patch also allows existing
exception-table fixups to handle known in-kernel accesses such as
load_unaligned_zeropad() while private memory remains mapped in the linear map.
The KVM CCA v17 integration branch is available here:
[0] https://gitlab.arm.com/linux-arm/linux-cca.git cca/cca-host/kvm-integration/v17
Steven Price (1):
arm64: mm: Handle Granule Protection Faults (GPFs)
arch/arm64/mm/fault.c | 28 ++++++++++++++++++++++------
1 file changed, 22 insertions(+), 6 deletions(-)
--
2.43.0
next reply other threads:[~2026-09-07 16:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-07 16:22 Suzuki K Poulose [this message]
2026-09-07 16:22 ` [PATCH v17 1/1] arm64: mm: Handle Granule Protection Faults (GPFs) Suzuki K Poulose
2026-09-10 17:45 ` Catalin Marinas
2026-09-10 18:52 ` Suzuki K Poulose
2026-09-11 13:02 ` [PATCH v17 0/1] " Will Deacon
2026-09-11 16:09 ` Suzuki K Poulose
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=20260907162204.1479401-1-suzuki.poulose@arm.com \
--to=suzuki.poulose@arm.com \
--cc=aneesh.kumar@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=gshan@redhat.com \
--cc=kvmarm@lists.linux.dev \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=maz@kernel.org \
--cc=pavan.kondeti@oss.qualcomm.com \
--cc=sdonthineni@nvidia.com \
--cc=steven.price@arm.com \
--cc=tabba@google.com \
--cc=will@kernel.org \
--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