Linux-ARM-Kernel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Steven Price <steven.price@arm.com>
To: Kohei Enju <enju.kohei@fujitsu.com>
Cc: kvm@vger.kernel.org, kvmarm@lists.linux.dev,
	Catalin Marinas <catalin.marinas@arm.com>,
	Marc Zyngier <maz@kernel.org>, Will Deacon <will@kernel.org>,
	James Morse <james.morse@arm.com>,
	Oliver Upton <oliver.upton@linux.dev>,
	Suzuki K Poulose <suzuki.poulose@arm.com>,
	Zenghui Yu <yuzenghui@huawei.com>,
	linux-arm-kernel@lists.infradead.org,
	linux-kernel@vger.kernel.org, Joey Gouly <joey.gouly@arm.com>,
	Alexandru Elisei <alexandru.elisei@arm.com>,
	Christoffer Dall <christoffer.dall@arm.com>,
	Fuad Tabba <tabba@google.com>,
	linux-coco@lists.linux.dev,
	Ganapatrao Kulkarni <gankulkarni@os.amperecomputing.com>,
	Gavin Shan <gshan@redhat.com>,
	Shanker Donthineni <sdonthineni@nvidia.com>,
	Alper Gun <alpergun@google.com>,
	"Aneesh Kumar K . V" <aneesh.kumar@kernel.org>,
	Emi Kisanuki <fj0570is@fujitsu.com>,
	Vishal Annapurve <vannapurve@google.com>,
	WeiLin.Chang@arm.com, Lorenzo Pieralisi <lpieralisi@kernel.org>
Subject: Re: [PATCH v2 00/12] KVM: arm64: CCA: Prepare Realm memory management
Date: Thu, 12 Nov 2026 09:41:26 +0000	[thread overview]
Message-ID: <a25321ce-7593-4c75-a529-e19c273638ef@arm.com> (raw)
In-Reply-To: <avV-P2_fOkFWQVnM@FCCLS0092175.localdomain>

On 12/11/2026 09:08, Kohei Enju wrote:
> Hi Steve,

Hi Kohei,

> On 11/11 14:57, Steven Price wrote:
>> This series adds the memory management plumbing for CCA, building on the
>> basic RMM support [1]. Thank you to those who reviewed v1 - I'm
>> attempted to address all the comments.
>>
>> The patches introduce internal Realm VM state and RMI feature checks,
>> prepare Realm stage-2 setup and teardown, and provide RTT mapping and
>> invalidation helpers. Realm memslots are restricted to the lower half
>> of the IPA space because the protected and shared halves alias each
>> other. The final patch connects the helpers to KVM's stage-2 MMU
>> operations.
>>
>> This is the memory management portion of the larger Realm host series.
>> Realm descriptor creation, REC entry and exit, activation, and the new
>> uAPI follow in the integration stack. This series alone does not enable
>> Realm creation.
>>
>> As before there's an integration branch[2] that includes the realm
>> creation, REC entry/exit etc building on top of this series. I've also
>> pushed a git branch[3] of just this series.
>>
>> Changes since v1:
>> - Add a guest_memfd prerequisite patch that checks whether the backing
>>   file supports mmap when preparing an arm64 memslot.
>> - Combine the RMI availability and feature checks into one patch, and
>>   move Realm vCPU feature restrictions to the integration stack.
>> - Correct Realm IPA sizing and RTT teardown, including teardown before
>>   activation, RTT accounting, and handling of missing or folded RTTs.
>> - Rework RTT mapping to respect IPA and physical alignment, handle
>>   partial RMI progress, and retry interrupted operations.
>> - Preserve private mappings when a Realm guest_memfd memslot deletion is
>>   rejected, and tighten Realm fault handling and stage-2 destruction.
>>
>> [1] https://lore.kernel.org/all/20261007073537.2454351-1-suzuki.poulose@arm.com/
>> [2] https://gitlab.arm.com/linux-arm/linux-cca
>>     branch: cca-host-mm/v2/integration
>> [3] https://gitlab.arm.com/linux-arm/linux-cca
>>     branch: cca-host-mm/v2/mm
>>
>> Steven Price (7):
>>   KVM: arm64: CCA: Reserve the RMM mode
>>   KVM: arm64: guest_memfd: Check mmap support when preparing memslot
>>   KVM: arm64: CCA: Check RMI support and features at init
>>   KVM: arm64: CCA: Add basic infrastructure for creating a realm
>>   KVM: arm64: CCA: Tear down RTTs
>>   KVM: arm64: CCA: Add Realm RTT mapping and invalidation helpers
>>   KVM: arm64: CCA: Support runtime faulting of memory
>>
>> Suzuki K Poulose (5):
>>   KVM: arm64: CCA: Introduce Realms
>>   KVM: arm64: Handle attributes in stage2_unmap_range
>>   KVM: Allow architectures to reject memslot changes before invalidation
>>   KVM: arm64: CCA: Prevent memslot modifications after Realm creation
>>   KVM: arm64: CCA: Add Realm stage-2 MMU operations
> 
> I've tested the integration branch [2] including this series on our
> hardware using the QEMU-VMM proposed in:
>   https://lore.kernel.org/qemu-devel/20261002202026.1204110-1-mathieu.poirier@linaro.org/
> 
> The Realm guest VM (32 vCPUs, 16 GiB RAM) booted successfully. To
> exercise the guest with a more realistic workload, I also performed a
> full Linux kernel build, which completed successfully.

Awesome - thank you very much for testing.

> A Tested-by tag might not be carried over to the next revision, if any,
> but anyway, for this series:
> 
> Tested-by: Kohei Enju <enju.kohei@fujitsu.com>

Thanks,
Steve



      reply	other threads:[~2026-11-12  9:41 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-11 14:57 [PATCH v2 00/12] KVM: arm64: CCA: Prepare Realm memory management Steven Price
2026-11-11 14:57 ` [PATCH v2 01/12] KVM: arm64: CCA: Reserve the RMM mode Steven Price
2026-11-11 14:57 ` [PATCH v2 02/12] KVM: arm64: guest_memfd: Check mmap support when preparing memslot Steven Price
2026-11-11 15:21   ` Suzuki K Poulose
2026-11-12 10:43     ` Steven Price
2026-11-12 16:35       ` Suzuki K Poulose
2026-11-12 16:57         ` Suzuki K Poulose
2026-11-11 14:57 ` [PATCH v2 03/12] KVM: arm64: CCA: Introduce Realms Steven Price
2026-11-11 14:57 ` [PATCH v2 04/12] KVM: arm64: CCA: Check RMI support and features at init Steven Price
2026-11-12 16:39   ` Suzuki K Poulose
2026-11-11 14:57 ` [PATCH v2 05/12] KVM: arm64: Handle attributes in stage2_unmap_range Steven Price
2026-11-11 14:57 ` [PATCH v2 06/12] KVM: arm64: CCA: Add basic infrastructure for creating a realm Steven Price
2026-11-11 14:57 ` [PATCH v2 07/12] KVM: arm64: CCA: Tear down RTTs Steven Price
2026-11-11 14:57 ` [PATCH v2 08/12] KVM: arm64: CCA: Add Realm RTT mapping and invalidation helpers Steven Price
2026-11-11 14:57 ` [PATCH v2 09/12] KVM: Allow architectures to reject memslot changes before invalidation Steven Price
2026-11-11 14:57 ` [PATCH v2 10/12] KVM: arm64: CCA: Prevent memslot modifications after Realm creation Steven Price
2026-11-11 14:57 ` [PATCH v2 11/12] KVM: arm64: CCA: Support runtime faulting of memory Steven Price
2026-11-11 14:57 ` [PATCH v2 12/12] KVM: arm64: CCA: Add Realm stage-2 MMU operations Steven Price
2026-11-12  9:08 ` [PATCH v2 00/12] KVM: arm64: CCA: Prepare Realm memory management Kohei Enju
2026-11-12  9:41   ` Steven Price [this message]

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=a25321ce-7593-4c75-a529-e19c273638ef@arm.com \
    --to=steven.price@arm.com \
    --cc=WeiLin.Chang@arm.com \
    --cc=alexandru.elisei@arm.com \
    --cc=alpergun@google.com \
    --cc=aneesh.kumar@kernel.org \
    --cc=catalin.marinas@arm.com \
    --cc=christoffer.dall@arm.com \
    --cc=enju.kohei@fujitsu.com \
    --cc=fj0570is@fujitsu.com \
    --cc=gankulkarni@os.amperecomputing.com \
    --cc=gshan@redhat.com \
    --cc=james.morse@arm.com \
    --cc=joey.gouly@arm.com \
    --cc=kvm@vger.kernel.org \
    --cc=kvmarm@lists.linux.dev \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-coco@lists.linux.dev \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=maz@kernel.org \
    --cc=oliver.upton@linux.dev \
    --cc=sdonthineni@nvidia.com \
    --cc=suzuki.poulose@arm.com \
    --cc=tabba@google.com \
    --cc=vannapurve@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