[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20251027191729.1704744-1-yeoreum.yun@arm.com>
Date: Mon, 27 Oct 2025 19:17:27 +0000
From: Yeoreum Yun <yeoreum.yun@....com>
To: maz@...nel.org,
oliver.upton@...ux.dev,
joey.gouly@....com,
suzuki.poulose@....com,
yuzenghui@...wei.com,
catalin.marinas@....com,
will@...nel.org,
perlarsen@...gle.com,
ayrton@...gle.com
Cc: linux-arm-kernel@...ts.infradead.org,
kvmarm@...ts.linux.dev,
linux-kernel@...r.kernel.org,
Yeoreum Yun <yeoreum.yun@....com>
Subject: [PATCH 0/2] use TPM device with CRB over FF-A when kernel boot with pkvm
To use TPM device iwth CRB over FF-A, it would be good to be compiled:
- CONFIG_ARM_FFA_TRANSPORT as bulit-in
- CONFIG_TCG_ARM_CRB_FFA as built-in
to integrate with IMA subsystem otherwise, it couldn't generate the
boot_aggreate log with the PCR value.
Unfortuately, kernel fails to probe the TPM device
when it boots with kvm-arm.mode=protected since the FF-A calls
(FFA_SEND_DIRECT_MSG/MSG2) are failed when CONFIG_ARM_FFA_TRANSPORT=y.
This patch series resolves failure of the TPM device when
kernel boots with kvm-arm.mode=protected and based on v6.18-rc3.
Yeoreum Yun (2):
KVM: arm64: fix FF-A call failure when ff-a driver is built-in
KVM: arm64: support optional calls of FF-A v1.2
arch/arm64/kvm/hyp/nvhe/ffa.c | 31 ++++++++++++++++++++++++++++++-
1 file changed, 30 insertions(+), 1 deletion(-)
base-commit: dcb6fa37fd7bc9c3d2b066329b0d27dedf8becaa
--
LEVI:{C3F47F37-75D8-414A-A8BA-3980EC8A46D7}
Powered by blists - more mailing lists