From: Mostafa Saleh <smostafa@google.com>
To: linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org
Cc: akpm@linux-foundation.org, catalin.marinas@arm.com,
will@kernel.org, rppt@kernel.org, maz@kernel.org,
aneesh.kumar@kernel.org, Mostafa Saleh <smostafa@google.com>
Subject: [PATCH 0/3] arm64/coco: Convert pKVM to a CC platform
Date: Wed, 3 Jun 2026 11:05:19 +0000 [thread overview]
Message-ID: <20260603110522.3331819-1-smostafa@google.com> (raw)
The goal of series is to convert pKVM as a CC platform similar to
ARM CCA, that makes CC guests consistently discovered which avoid
breaking it by the ongoing DMA rework [1]
The first patch is a minor clean up I noticed while reading the code.
And the second patch is a bug fix found by Sashiko.
The third patch is the main one.
[1]https://lore.kernel.org/all/20260522042815.370873-1-aneesh.kumar@kernel.org/
Mostafa Saleh (3):
arm64/mm: Simplify SWIOTLB setup in arch_mm_preinit()
drivers/virt: pkvm: Fix end calculation in mmio_guard_ioremap_hook()
arm64/coco: Add pKVM as a CC platform
arch/arm64/include/asm/hypervisor.h | 13 ++++++++++
arch/arm64/include/asm/mem_encrypt.h | 3 ++-
arch/arm64/kernel/rsi.c | 12 ---------
arch/arm64/mm/init.c | 26 +++++++++++++------
drivers/virt/coco/pkvm-guest/arm-pkvm-guest.c | 5 +++-
5 files changed, 37 insertions(+), 22 deletions(-)
--
2.54.0.1032.g2f8565e1d1-goog
next reply other threads:[~2026-06-03 11:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 11:05 Mostafa Saleh [this message]
2026-06-03 11:05 ` [PATCH 1/3] arm64/mm: Simplify SWIOTLB setup in arch_mm_preinit() Mostafa Saleh
2026-06-03 12:27 ` Mike Rapoport
2026-06-03 13:13 ` Mostafa Saleh
2026-06-03 11:05 ` [PATCH 2/3] drivers/virt: pkvm: Fix end calculation in mmio_guard_ioremap_hook() Mostafa Saleh
2026-06-03 11:05 ` [PATCH 3/3] arm64/coco: Add pKVM as a CC platform Mostafa Saleh
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=20260603110522.3331819-1-smostafa@google.com \
--to=smostafa@google.com \
--cc=akpm@linux-foundation.org \
--cc=aneesh.kumar@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maz@kernel.org \
--cc=rppt@kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox