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 4F9713B6BE6; Wed, 25 Mar 2026 10:18:10 +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=1774433895; cv=none; b=DfvBikOdC4ovdv9t/OP4c1ivJLV72hUrq9PnyncI3P2VN4g0SSfgslKWVqs/tkx7mJG0oEdytk7z+1//OFSthpnb5Ufnd8CizHuh0c112L0abx3TS+a+PYRFkqFvTIVzQrcJaqXKMKcY/rzkoijYPHJivkkM/W0r4Jo2qv/7RmE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1774433895; c=relaxed/simple; bh=LC/v5hyd/W73lE56Dbp7kdnqaJWcyniIrrWkSFekdKI=; h=Message-ID:Date:MIME-Version:Subject:To:Cc:References:From: In-Reply-To:Content-Type; b=iuDWLH52oYVFx5ze+0tQbdAID4jg4ChmWAEZ1vvQQbkB1PKGWsC57n47b+A5hmXP1VlpRqC2nZJa9GXVLLwgMyBt4PNxs51EJg9ig+qCVtPKRVvdSuGa34oXW0pzR9YOZHCIRMFc/g6WK6le9qbuRdNzwl2Z0nTAiLBlGjbDY10= 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=Biqyx7ZN; 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="Biqyx7ZN" 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 3619316F2; Wed, 25 Mar 2026 03:18:03 -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 4488B3F836; Wed, 25 Mar 2026 03:18:06 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=arm.com; s=foss; t=1774433889; bh=LC/v5hyd/W73lE56Dbp7kdnqaJWcyniIrrWkSFekdKI=; h=Date:Subject:To:Cc:References:From:In-Reply-To:From; b=Biqyx7ZNA8b96Qa8f6Ai6NrC0kDDpV4XPbO+NJ3K8yhCVck8MOhtOhe6VouMYJVXf +eN2oXcGyf9PZ+tH3zeyyzoKc5ERU6KBOnCBb+3Ud3vqznCeWc/Yalr+o1VhZddjYW I0bunVmnqB1aTrHuI1qus9pqdkVzezI8aSIvwLa4= Message-ID: <9247d9ea-64b4-4e8e-81f8-3c8e00750acf@arm.com> Date: Wed, 25 Mar 2026 10:16:33 +0000 Precedence: bulk X-Mailing-List: linux-coco@lists.linux.dev 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 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> From: Suzuki K Poulose In-Reply-To: <0b7121e7-3c74-4303-a200-01d2b7c535ce@redhat.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit 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. --8>-- diff --git a/tools/shrinkwrap/configs/cca.yaml b/tools/shrinkwrap/configs/cca.yaml index 1c0455ba..0d70a582 100644 --- a/tools/shrinkwrap/configs/cca.yaml +++ b/tools/shrinkwrap/configs/cca.yaml @@ -25,8 +25,8 @@ build: linux: repo: - remote: https://gitlab.geo.arm.com/software/linux-arm/fkvm.git - revision: stepri01/cca/v13-wip+sro + remote: https://gitlab.arm.com/linux-arm/linux-cca + revision: cca-host/v13 prebuild: - ./scripts/config --file ${param:builddir}/.config --enable CONFIG_PCI_TSM - ./scripts/config --file ${param:builddir}/.config --enable CONFIG_PCI_DOE @@ -50,5 +50,5 @@ build: remote: https://git.kernel.org/pub/scm/utils/dtc/dtc.git revision: v1.7.2 kvmtool: - remote: https://gitlab.geo.arm.com/software/linux-arm/fkvmtool.git - revision: stepri01/cca/v13-wip + remote: https://gitlab.arm.com/linux-arm/kvmtool-cca + revision: cca/v11 Kind regards Suzuki > > Thanks, > Gavin > > >