From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-pf1-f193.google.com (mail-pf1-f193.google.com [209.85.210.193]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C195C13777E for ; Thu, 12 Feb 2026 17:48:51 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.210.193 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770918533; cv=none; b=CmR9P1NNHk0xA6vPHocySMf14l8i4dxD18xTDmYERLsVj5KhlkDh5LDD8a83tVLLL55zKOPLilGo3zOlEJ/oAD9F0cgfq+f+S2IMu3mP3S2CCspFxDWV8DYLDBWaJdtWDHokGSjbaKoRsjGCBcNctxsIYbEoMNMqXpaoCgZ2d9w= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770918533; c=relaxed/simple; bh=Y9YqPnc8BmjwKubmvFSXt3QWfkXvZK4RllFw60PzH/E=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=aY8XJsGvASMGPDIO/4mbCJag9neFQPl4UYwbAV/w4GlDvKTvVW23OLc81h9YtSgrf4jvT+Z5pjs7XEp3nmK0V3AHjP2mok7yXXhbOfuRAdQqPhciV/L34o9UPmJoIAck8F3Nu3vwuJ8f5jhN76nw0FEUz6g5I3aXFxcwhWGWKtk= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linaro.org; spf=pass smtp.mailfrom=linaro.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b=SfcxCpys; arc=none smtp.client-ip=209.85.210.193 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=linaro.org Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=linaro.org Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="SfcxCpys" Received: by mail-pf1-f193.google.com with SMTP id d2e1a72fcca58-8231061d234so92139b3a.1 for ; Thu, 12 Feb 2026 09:48:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1770918531; x=1771523331; darn=vger.kernel.org; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=wkYX9/8AMpNKTzDUSgXfqQoLj53MIkWsoktK8rnuztU=; b=SfcxCpysIslfaeRb0koLoQJIzCPa4PzVqhpQYLJLlQEEktnR8ldYrI8r0eg5Nic1so bmVt3dW7/S/+2TzIV+uym8efWN7BJRE5cBmr7dr5VpVQuxKaT3GvcccEn12cIRwyivTq W5spevx+CVXEB60hyFCYpX3MJM1cPteJFA4TWsBU67O0z00OglzlE7XZ8Y+1wRkg/Nze pXM6qpTMgs5nD8ib0dp6wViNMw4bPsLuvf8ybDF95tdTS42YzoQ6gX0EbS8gJ9Jb1pzm XBOdZQOjXbiljZeEqTeezrVWIYSv9xmwyESdOmcu73FrXG3OERuU1jKCJP+ba/Az/66l y+Cw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1770918531; x=1771523331; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-gg:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=wkYX9/8AMpNKTzDUSgXfqQoLj53MIkWsoktK8rnuztU=; b=pXLuL5Fz/qjJ8zjWFd7cltN8jLHdJ1hVsxt4eMeCD+JfxdccIVmhrSruBb/9YeQX58 ru9WFOF+pQA7QJtr1npLZjIaU/k7IQRq0sULAicOXgoa94+8T/DIvvsfQRrscbpKppmf 9eBfGKmOc90s4whKaLZo9V55aVKGNzoCzq71VB3LVQYEUzGyp8Z1T3A3QoUZW8cN2HPa TkVDHQu90fBJKIvK89pYbgVfiCWZEThtfGrUHOSLmCKYwFEhcMWXhnkOVESyjcRPL7/Q i4asOSmMRVW1NRqt1swtUvS8RFY6Ig2mJ5eMaEbP09U+INfhuZSbbxKlvW8XuZN5XMo0 SqXg== X-Forwarded-Encrypted: i=1; AJvYcCV+i6PTKYTsHztW57OoZWt8TJDaQkmIo9XEAJmjLkFPTrpIbe6A0QE7Hy6WDASj6hu17yCp6/iif9e76DY=@vger.kernel.org X-Gm-Message-State: AOJu0Yz+tdvL1wtLbfU/F8dQkHPipVLRVOFOQyDb1yZ48yDQvBIaco9e kZwGuNduQ1Z4ZNICpTrQHgka5hLv+s+Rke9cXhM5Z8Pg63tMf7A/aZvJUE4g1WmfaAo= X-Gm-Gg: AZuq6aJYCVJATXKMmHGl8EvNiOt12oOPv6G8I+xL61JJI0gHOW0qXJ+4jHbsbwqPFp3 R7XjSjveshPXG+0wf3LKjMdoz986vvFKa6xVSnXT10Vf90ZmO8LO10nVHep25tJ5Lg9hWI9s+vD pWp22Jf6zzRLndCGxq6lAVLcf5Iy8Kd3qUa28i/Ef0KOyWn2mSZn/AhNHMGSC9veyTY1d+ENCag s7/O5fa5UcSPVK8y83bnxK1RRtP5sgr5wA7ydX7V9smD7ufz8VmHbXlT8wB8/ZOeO7XPoxZnDiE BPChpYxgo0N6v9NJEtorpnKClbpdoQE3fPEabzR6aGuy0dggaj5RrYKQDHwJpRc2wgKpd3wI7LM UPUnFzJyzrf+okMErlwNZEA9cIPJ7Kbv4D8THkNAPa94v4ZOjbVQAYvFBTGYJl7ai06bTxok+J4 i55M5gJcVjnB9IlndGGaOdhPR1NrM= X-Received: by 2002:a05:6a00:17a1:b0:824:a304:e5b7 with SMTP id d2e1a72fcca58-824b302d476mr3194178b3a.51.1770918530788; Thu, 12 Feb 2026 09:48:50 -0800 (PST) Received: from p14s ([2604:3d09:148c:c800:b17f:2662:e1ea:5d37]) by smtp.gmail.com with ESMTPSA id d2e1a72fcca58-8249e3bd3b2sm6231651b3a.22.2026.02.12.09.48.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Thu, 12 Feb 2026 09:48:50 -0800 (PST) Date: Thu, 12 Feb 2026 10:48:47 -0700 From: Mathieu Poirier To: Steven Price Cc: kvm@vger.kernel.org, kvmarm@lists.linux.dev, 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 Subject: Re: [PATCH v12 00/46] arm64: Support for Arm CCA in KVM Message-ID: References: <20251217101125.91098-1-steven.price@arm.com> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20251217101125.91098-1-steven.price@arm.com> Hi Steven, On Wed, Dec 17, 2025 at 10:10:37AM +0000, Steven Price wrote: > This series adds support for running protected VMs using KVM under the > Arm Confidential Compute Architecture (CCA). I've changed the uAPI > following feedback from Marc. > > The main change is that rather than providing a multiplex CAP and > expecting the VMM to drive the different stages of realm construction, > there's now just a minimal interface and KVM performs the necessary > operations when needed. > > This series is lightly tested and is meant as a demonstration of the new > uAPI. There are a number of (known) rough corners in the implementation > that I haven't dealt with properly. > > In particular please note that this series is still targetting RMM v1.0. > There is an alpha quality version of RMM v2.0 available[1]. Feedback was > that there are a number of blockers for merging with RMM v1.0 and so I > expect to rework this series to support RMM v2.0 before it is merged. > That will necessarily involve reworking the implementation. > > Specifically I'm expecting improvements in: > > * GIC handling - passing state in registers, and allowing the host to > fully emulate the GIC by allowing trap bits to be set. > > * PMU handling - again providing flexibility to the host's emulation. > > * Page size/granule size mismatch. RMM v1.0 defines the granule as 4k, > RMM v2.0 provide the option for the host to change the granule size. > The intention is that Linux would simply set the granule size equal > to its page size which will significantly simplify the management of > granules. > > * Some performance improvement from the use of range-based map/unmap > RMI calls. > > This series is based on v6.19-rc1. It is also available as a git > repository: > > https://gitlab.arm.com/linux-arm/linux-cca cca-host/v12 > > Work in progress changes for kvmtool are available from the git > repository below: > > https://gitlab.arm.com/linux-arm/kvmtool-cca cca/v10 The first thing to note is that branch cca/v10 does not compile due to function realm_configure_parameters() not being called anywhere. Marking the function as [[maybe_unused]] solved the problem on my side. Using the FVP emulator, booting a Realm that includes EDK2 in its boot stack worked. If EDK2 is not part of the boot stack and a kernel is booted directly from lkvm, mounting the initrd fails. Looking into this issue further, I see that from a Realm kernel's perspective, the content of the initrd is either encrypted or has been trampled on. I'd be happy to provide more details on the above, just let me know. Thanks, Mathieu > > [1] https://developer.arm.com/documentation/den0137/latest/ > > Jean-Philippe Brucker (7): > arm64: RMI: Propagate number of breakpoints and watchpoints to > userspace > arm64: RMI: Set breakpoint parameters through SET_ONE_REG > arm64: RMI: Initialize PMCR.N with number counter supported by RMM > arm64: RMI: Propagate max SVE vector length from RMM > arm64: RMI: Configure max SVE vector length for a Realm > arm64: RMI: Provide register list for unfinalized RMI RECs > arm64: RMI: Provide accurate register list > > Joey Gouly (2): > arm64: RMI: allow userspace to inject aborts > arm64: RMI: support RSI_HOST_CALL > > Steven Price (34): > arm64: RME: Handle Granule Protection Faults (GPFs) > arm64: RMI: Add SMC definitions for calling the RMM > arm64: RMI: Add wrappers for RMI calls > arm64: RMI: Check for RMI support at KVM init > arm64: RMI: Define the user ABI > arm64: RMI: Basic infrastructure for creating a realm. > KVM: arm64: Allow passing machine type in KVM creation > arm64: RMI: RTT tear down > arm64: RMI: Activate realm on first VCPU run > arm64: RMI: Allocate/free RECs to match vCPUs > KVM: arm64: vgic: Provide helper for number of list registers > arm64: RMI: Support for the VGIC in realms > KVM: arm64: Support timers in realm RECs > arm64: RMI: Handle realm enter/exit > arm64: RMI: Handle RMI_EXIT_RIPAS_CHANGE > KVM: arm64: Handle realm MMIO emulation > KVM: arm64: Expose support for private memory > arm64: RMI: Allow populating initial contents > arm64: RMI: Set RIPAS of initial memslots > arm64: RMI: Create the realm descriptor > arm64: RMI: Add a VMID allocator for realms > arm64: RMI: Runtime faulting of memory > KVM: arm64: Handle realm VCPU load > KVM: arm64: Validate register access for a Realm VM > KVM: arm64: Handle Realm PSCI requests > KVM: arm64: WARN on injected undef exceptions > arm64: Don't expose stolen time for realm guests > arm64: RMI: Always use 4k pages for realms > arm64: RMI: Prevent Device mappings for Realms > HACK: Restore per-CPU cpu_armpmu pointer > arm_pmu: Provide a mechanism for disabling the physical IRQ > arm64: RMI: Enable PMU support with a realm guest > KVM: arm64: Expose KVM_ARM_VCPU_REC to user space > arm64: RMI: Enable realms to be created > > Suzuki K Poulose (3): > kvm: arm64: Include kvm_emulate.h in kvm/arm_psci.h > kvm: arm64: Don't expose unsupported capabilities for realm guests > arm64: RMI: Allow checking SVE on VM instance > > Documentation/virt/kvm/api.rst | 78 +- > arch/arm64/include/asm/kvm_emulate.h | 31 + > arch/arm64/include/asm/kvm_host.h | 13 +- > arch/arm64/include/asm/kvm_rmi.h | 137 +++ > arch/arm64/include/asm/rmi_cmds.h | 508 ++++++++ > arch/arm64/include/asm/rmi_smc.h | 269 +++++ > arch/arm64/include/asm/virt.h | 1 + > arch/arm64/kernel/cpufeature.c | 1 + > arch/arm64/kvm/Kconfig | 2 + > arch/arm64/kvm/Makefile | 2 +- > arch/arm64/kvm/arch_timer.c | 37 +- > arch/arm64/kvm/arm.c | 179 ++- > arch/arm64/kvm/guest.c | 95 +- > arch/arm64/kvm/hypercalls.c | 4 +- > arch/arm64/kvm/inject_fault.c | 5 +- > arch/arm64/kvm/mmio.c | 16 +- > arch/arm64/kvm/mmu.c | 214 +++- > arch/arm64/kvm/pmu-emul.c | 6 + > arch/arm64/kvm/psci.c | 30 + > arch/arm64/kvm/reset.c | 13 +- > arch/arm64/kvm/rmi-exit.c | 207 ++++ > arch/arm64/kvm/rmi.c | 1663 ++++++++++++++++++++++++++ > arch/arm64/kvm/sys_regs.c | 53 +- > arch/arm64/kvm/vgic/vgic-init.c | 2 +- > arch/arm64/kvm/vgic/vgic-v2.c | 6 +- > arch/arm64/kvm/vgic/vgic-v3.c | 14 +- > arch/arm64/kvm/vgic/vgic.c | 55 +- > arch/arm64/kvm/vgic/vgic.h | 20 +- > arch/arm64/mm/fault.c | 28 +- > drivers/perf/arm_pmu.c | 20 + > include/kvm/arm_arch_timer.h | 2 + > include/kvm/arm_pmu.h | 4 + > include/kvm/arm_psci.h | 2 + > include/linux/perf/arm_pmu.h | 7 + > include/uapi/linux/kvm.h | 42 +- > 35 files changed, 3650 insertions(+), 116 deletions(-) > create mode 100644 arch/arm64/include/asm/kvm_rmi.h > create mode 100644 arch/arm64/include/asm/rmi_cmds.h > create mode 100644 arch/arm64/include/asm/rmi_smc.h > create mode 100644 arch/arm64/kvm/rmi-exit.c > create mode 100644 arch/arm64/kvm/rmi.c > > -- > 2.43.0 > >