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 3C25F3CEBBB; Wed, 25 Mar 2026 11:32:24 +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=1774438347; cv=none; b=cXBgNRdSlNwq3pNSJ4o4iijQNj1g23xxNE0DOotWPjOi/sPEp22cPHHhLIAmegtj41NXyx7iWSD01jIZ8z98l1D+w8A+sjgXwGMAmFuKCAdlPycofKv74qO+wUXOLUqlUXLJTxsLb/L/gDP54RJ0p1WkihSJMuZ6BG9T5HfB/kU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774438347; c=relaxed/simple; bh=CxcNnv3bvWvpaqMJwSfMUPZRdGgLZM5A+Xb79R5Z4oM=; h=Message-ID:Date:MIME-Version:Subject:From:To:Cc:References: In-Reply-To:Content-Type; b=cSu7JHe0qiGmwKcfYRljByQuvtaRNR5K3sXAeE3CnRaW1uuLpS+LcTEX3zfkFIJ6j1HbDVOiCcFh7CJ3UxHdIGIJ3lgr763eI17odBhVIzgcunp0snqdzDixOD+p+gkPxeRNRmh/tulN2P+J0W8D94jPSHeJ8ZBMmLZhrVNJ890= 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=FNR9beFU; 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="FNR9beFU" 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 9388F1CDD; Wed, 25 Mar 2026 04:32:17 -0700 (PDT) Received: from [10.57.19.213] (unknown [10.57.19.213]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id 200E93F915; Wed, 25 Mar 2026 04:32:19 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=arm.com; s=foss; t=1774438343; bh=CxcNnv3bvWvpaqMJwSfMUPZRdGgLZM5A+Xb79R5Z4oM=; h=Date:Subject:From:To:Cc:References:In-Reply-To:From; b=FNR9beFUs8r+ioyNQ89JAQIsEcDy8ieVpjLH77MUhzSPkgAIBpEKEezItjyRGacZz +wCtsWOS53DhjqpQojZrW0hOjl0qsrIsLNCBmP8YwfmdWZXB3MnV6tOOPHb/dd6mpc AHpNhzvLWmD2fO70m0FSmJrKvlqbSr7cxBgFNxmU= Message-ID: <70fb8f35-1874-421a-87f9-5adf53f41ba2@arm.com> Date: Wed, 25 Mar 2026 11:32:18 +0000 Precedence: bulk X-Mailing-List: kvm@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v13 00/48] arm64: Support for Arm CCA in KVM Content-Language: en-GB From: Suzuki K Poulose To: Gavin Shan , Steven Price , Mathieu Poirier Cc: kvm@vger.kernel.org, kvmarm@lists.linux.dev, Catalin Marinas , Marc Zyngier , Will Deacon , James Morse , Oliver Upton , 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 , Shanker Donthineni , Alper Gun , "Aneesh Kumar K . V" , Emi Kisanuki , Vishal Annapurve References: <20260318155413.793430-1-steven.price@arm.com> <37bc1222-6fc7-48f0-94d3-6eaac420aa55@arm.com> <0b7121e7-3c74-4303-a200-01d2b7c535ce@redhat.com> <9247d9ea-64b4-4e8e-81f8-3c8e00750acf@arm.com> In-Reply-To: <9247d9ea-64b4-4e8e-81f8-3c8e00750acf@arm.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit On 25/03/2026 10:16, Suzuki K Poulose wrote: > Hi Gavin > > Steven is on holidays, so I am jumping in here. > > On 25/03/2026 06:37, Gavin Shan wrote: >> Hi Steven, >> >> On 3/21/26 2:45 AM, Steven Price wrote: >>> On 19/03/2026 23:02, Mathieu Poirier wrote: >> >> [...] >> >>>>> >>>>> The TF-RMM has not yet merged the RMMv2.0 support, so you will need to >>>>> use the following branch: >>>>> >>>>> https://git.trustedfirmware.org/TF-RMM/tf-rmm.git topics/rmm-v2.0-poc >>>> >>>> This RMM version is expecting a RMM EL3 interface version of at >>>> least 2.0.  Do >>>> you have a TF-A to use with it? >>> >>> You should be able to use the 'master' branch of the TF-A repository. >>> For now you need to set RMM_V1_COMPAT=0 to enable 2.0 support. >>> >> >> In upstream TF-A repository [1], I don't see the config option >> 'RMM_V1_COMPAT'. >> would it be something else? >> >> [1] git@github.com:ARM-software/arm-trusted-firmware.git    (branch: >> master) >> > > suzuki@ewhatever:trusted-firmware-a$ git grep RMM_V1_COMPAT > Makefile:       RMM_V1_COMPAT \ > Makefile:       RMM_V1_COMPAT \ > docs/getting_started/build-options.rst:-  ``RMM_V1_COMPAT``: Boolean > flag to enable support for RMM v1.x compatibility > include/services/rmmd_svc.h:#if RMM_V1_COMPAT > include/services/rmmd_svc.h:#endif /* RMM_V1_COMPAT */ > make_helpers/defaults.mk:RMM_V1_COMPAT                  := 1 > services/std_svc/rmmd/rmmd_main.c:#if RMM_V1_COMPAT > services/std_svc/rmmd/rmmd_main.c:#if RMM_V1_COMPAT > services/std_svc/rmmd/rmmd_main.c:#if !RMM_V1_COMPAT > services/std_svc/rmmd/rmmd_main.c:#if RMM_V1_COMPAT > services/std_svc/rmmd/rmmd_main.c:#if RMM_V1_COMPAT > services/std_svc/rmmd/rmmd_main.c:#if RMM_V1_COMPAT > services/std_svc/rmmd/rmmd_rmm_lfa.c:#if RMM_V1_COMPAT > services/std_svc/rmmd/rmmd_rmm_lfa.c:#if RMM_V1_COMPAT > services/std_svc/rmmd/rmmd_rmm_lfa.c:#if RMM_V1_COMPAT > services/std_svc/rmmd/rmmd_rmm_lfa.c:#if RMM_V1_COMPAT > suzuki@ewhatever:trusted-firmware-a$ git log --oneline -1 > 8dae0862c (HEAD, origin/master, origin/integration, origin/HEAD) Merge > changes from topic "qti_lemans_evk" into integration > suzuki@ewhatever:trusted-firmware-a$ git remote get-url origin > https://git.trustedfirmware.org/TF-A/trusted-firmware-a.git > > > >> I use the following command to build TF-A image. The RMM-EL3 >> compatible issue is >> still seen. >> >>      TFA_PATH=$PWD >>      EDK2_IMAGE=${TFA_PATH}/../edk2/Build/ArmVirtQemuKernel-AARCH64/ >> RELEASE_GCC5/FV/QEMU_EFI.fd >>      RMM_IMAGE=${TFA_PATH}/../tf-rmm/build-qemu/Debug/rmm.img >>      make CROSS_COMPILE=aarch64-none-elf-                               \ >>           PLAT=qemu ENABLE_RME=1 RMM_V1_COMPAT=0 DEBUG=1 LOG_LEVEL=40   \ >>           QEMU_USE_GIC_DRIVER=QEMU_GICV3                                \ >>           BL33=${EDK2_IMAGE} RMM=${RMM_IMAGE}                           \ >>           -j 8 all fip >> > > > > >> Booting messages >> ================ >> INFO:    BL31: Initializing runtime services >> INFO:    RMM setup done. >> INFO:    BL31: Initializing RMM >> INFO:    RMM init start. >> ERROR:   RMM init failed: -2 >> WARNING: BL31: RMM initialization failed > > This is definitely the TF-A RMM incompatibility. > > Btw, the shrinkwrap overlay configs in tf-RMM repository should work. > But unfortunately the Linux/kvmtool repositories are pointing to > internal repositories. The following patch should fix it and get > it all working. I am working with the tf-rmm team to fix this. This is now fixed in the branch : https://git.trustedfirmware.org/plugins/gitiles/TF-RMM/tf-rmm/+/refs/heads/topics/rmm-v2.0-poc/tools/shrinkwrap/configs/cca.yaml Cheers Suzuki