From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from foss.arm.com (foss.arm.com [217.140.110.172]) by smtp.subspace.kernel.org (Postfix) with ESMTP id 7AF543890F6; Wed, 15 Jul 2026 14:29:23 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=217.140.110.172 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784125765; cv=none; b=UPfjdY0Z4K8IwXItltZfRCg6N+kLqQ8jpIxljKoLFRAvFgklYmaGmRSAXzEZMhzFvdHf0dQwYjfQtvzUn6ScFUPX9xQdXcO7PzqoTBAFEdFrz5tIGilIutUdWYqQM30MI4ZlRHEe3MAYHc2La9chZbR3QfX2mHoGsb57iwC2Ubg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1784125765; c=relaxed/simple; bh=Aq3mAH3poSFbImflFNQAkOr2RDqb2iCoUJzNSYta8b8=; h=From:To:Cc:Subject:Date:Message-ID:In-Reply-To:References: MIME-Version; b=Gg4wk+wT54wtMDw8J2/c56t0KmT3eyxD1qJMtZibhBlHdaHVIxKoMeWRtFQUVYz2wiG0RzBVG5bW/RIc1lVYm/2UCyIBhmKK3qKMWoqttBYrtN62ioJBNxF1xtFIAoLfDQCRwgIzA/soVkPKzT/OKsnk+ZrPCHIxk8zPo8f76Cg= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com; spf=pass smtp.mailfrom=arm.com; dkim=pass (1024-bit key) header.d=arm.com header.i=@arm.com header.b=mqg01ire; arc=none smtp.client-ip=217.140.110.172 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=arm.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=arm.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=arm.com header.i=@arm.com header.b="mqg01ire" Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 981861576; Wed, 15 Jul 2026 07:29:18 -0700 (PDT) Received: from e122027.cambridge.arm.com (e122027.cambridge.arm.com [10.1.25.27]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 2C5A33F7B4; Wed, 15 Jul 2026 07:29:18 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=arm.com; s=foss; t=1784125762; bh=Aq3mAH3poSFbImflFNQAkOr2RDqb2iCoUJzNSYta8b8=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=mqg01ireFUQuau+Jq/lxkK2DmZz8g+6xcHbQFdwNnJY70ENUgp+eJZbnndvwKFmo+ 6LyiP9k2YrmabTXrvxVfiyA27QDCp/tHOFlhCi/z3fwCod7axxSgocMmaQurcBR44i mdLZkJaAQED8zGKy2lEEaS4D4L45h0+PG2lh21yA= From: Steven Price To: kvm@vger.kernel.org, kvmarm@lists.linux.dev Cc: Steven Price , Catalin Marinas , Marc Zyngier , Will Deacon , James Morse , Oliver Upton , Suzuki K Poulose , Zenghui Yu , linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org, Joey Gouly , Alexandru Elisei , Christoffer Dall , Fuad Tabba , linux-coco@lists.linux.dev, Ganapatrao Kulkarni , Gavin Shan , Shanker Donthineni , Alper Gun , "Aneesh Kumar K . V" , Emi Kisanuki , Vishal Annapurve , WeiLin.Chang@arm.com, Lorenzo Pieralisi Subject: [PATCH v15 06/37] KVM: arm64: CCA: Define the user ABI Date: Wed, 15 Jul 2026 15:28:08 +0100 Message-ID: <20260715142841.80544-7-steven.price@arm.com> X-Mailer: git-send-email 2.43.0 In-Reply-To: <20260715142841.80544-1-steven.price@arm.com> References: <20260715142841.80544-1-steven.price@arm.com> Precedence: bulk X-Mailing-List: linux-coco@lists.linux.dev List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit There is one CAP (KVM_CAP_ARM_RMI) which identifies the presence of CCA, and one ioctl. The ioctl (KVM_ARM_RMI_POPULATE) is used to populate memory during creation of the realm as this requires the RMM to copy data from an unprotected address to the protected memory - CCA does not support shared <-> private memory conversion where the memory contents is preserved as this is incompatible with memory encryption. Signed-off-by: Steven Price --- Changes since v13: * KVM_ARM_VCPU_RMI_PSCI_COMPLETE removed. * KVM_ARM_RMI_POPULATE documentation updated to reflect that the structure is written by the kernel. * CAP number bumped. Changes since v12: * Change KVM_ARM_RMI_POPULATE to update the structure with the amount that has been progressed rather than return the number of bytes populated. * Describe the flag KVM_ARM_RMI_POPULATE_FLAGS_MEASURE. * CAP number is bumped. * NOTE: The PSCI ioctl may be removed in a future spec release. Changes since v11: * Completely reworked to be more implicit. Rather than having explicit CAP operations to progress the realm construction these operations are done when needed (on populating and on first vCPU run). * Populate and PSCI complete are promoted to proper ioctls. Changes since v10: * Rename symbols from RME to RMI. Changes since v9: * Improvements to documentation. * Bump the magic number for KVM_CAP_ARM_RME to avoid conflicts. Changes since v8: * Minor improvements to documentation following review. * Bump the magic numbers to avoid conflicts. Changes since v7: * Add documentation of new ioctls * Bump the magic numbers to avoid conflicts Changes since v6: * Rename some of the symbols to make their usage clearer and avoid repetition. Changes from v5: * Actually expose the new VCPU capability (KVM_ARM_VCPU_REC) by bumping KVM_VCPU_MAX_FEATURES - note this also exposes KVM_ARM_VCPU_HAS_EL2! --- Documentation/virt/kvm/api.rst | 41 ++++++++++++++++++++++++++++++++++ include/uapi/linux/kvm.h | 13 +++++++++++ 2 files changed, 54 insertions(+) diff --git a/Documentation/virt/kvm/api.rst b/Documentation/virt/kvm/api.rst index 304b9c3209ae..b38e090ad95d 100644 --- a/Documentation/virt/kvm/api.rst +++ b/Documentation/virt/kvm/api.rst @@ -6642,6 +6642,38 @@ if the guest_memfd memory was pinned in IOMMU page tables. See also: :ref: `KVM_SET_MEMORY_ATTRIBUTES`. +4.146 KVM_ARM_RMI_POPULATE +-------------------------- + +:Capability: KVM_CAP_ARM_RMI +:Architectures: arm64 +:Type: vm ioctl +:Parameters: struct kvm_arm_rmi_populate (in/out) +:Returns: 0 on success, < 0 on error + +:: + + struct kvm_arm_rmi_populate { + __u64 base; + __u64 size; + __u64 source_uaddr; + __u32 flags; + __u32 reserved; + }; + +Populate a region of protected address space by copying the data from the +(non-protected) user space pointer provided into a protected region (backed by +guestmem_fd). It implicitly sets the destination region to RIPAS RAM. This is +only valid before any VCPUs have been run. The ioctl might not populate the +entire region and in this case the kernel updates the fields `base`, `size` and +`source_uaddr`. User space may have to repeatedly call it until `size` is 0 to +populate the entire region. + +`flags` can be set to `KVM_ARM_RMI_POPULATE_FLAGS_MEASURE` to request that the +populated data is hashed and added to the guest's Realm Initial Measurement +(RIM) stored by the RMM. This can then be retrieved by the guest (using the RSI +interface) to present to an attestation server. + .. _kvm_run: 5. The kvm_run structure @@ -9025,6 +9057,15 @@ enabled, cmma can't be enabled anymore and pfmfi and the storage key interpretation are disabled. If cmma has already been enabled or the hpage_2g module parameter is not set to 1, -EINVAL is returned. +7.48 KVM_CAP_ARM_RMI +-------------------- + +:Architectures: arm64 +:Target: VM +:Parameters: None + +This capability indicates that support for CCA realms is available. + 8. Other capabilities. ====================== diff --git a/include/uapi/linux/kvm.h b/include/uapi/linux/kvm.h index 129d6f630325..0231ff174a50 100644 --- a/include/uapi/linux/kvm.h +++ b/include/uapi/linux/kvm.h @@ -998,6 +998,7 @@ struct kvm_enable_cap { #define KVM_CAP_S390_VSIE_ESAMODE 248 #define KVM_CAP_S390_HPAGE_2G 249 #define KVM_CAP_GUEST_MEMFD_MEMORY_ATTRIBUTES 250 +#define KVM_CAP_ARM_RMI 251 struct kvm_irq_routing_irqchip { __u32 irqchip; @@ -1686,4 +1687,16 @@ struct kvm_pre_fault_memory { __u64 padding[5]; }; +/* Available with KVM_CAP_ARM_RMI, only for VMs with KVM_VM_TYPE_ARM_REALM */ +#define KVM_ARM_RMI_POPULATE _IOWR(KVMIO, 0xd7, struct kvm_arm_rmi_populate) +#define KVM_ARM_RMI_POPULATE_FLAGS_MEASURE (1 << 0) + +struct kvm_arm_rmi_populate { + __u64 base; + __u64 size; + __u64 source_uaddr; + __u32 flags; + __u32 reserved; +}; + #endif /* __LINUX_KVM_H */ -- 2.43.0