From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 72153CA5FA5 for ; Tue, 29 Sep 2026 19:12:37 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=6qILHk4OykL5JVH8gBffyXwkhL7+oj5JL8bCPFt0024=; b=SJ/DAdzNl+k4hUMMCr+tLweMrs ZJ7IUAiLBoaJSN57Yj+1U9/fcL4EQEgOc8Z8bP/4K2/NKvlF3//sxgp2jHDNUjxTGG6hIVzdsmDok 3qOaW17JzKl67/m6rJ0GX/FvG+b6y/6gpMKj+44F2rNUOPUdm07VZZB05mh/dSMKwxboBCCFbgwkD KdMFYBAsozaBXwaezpQs+UNCcyLSAImi/tRgp/2P4wPE+ppgZ8AmaP2aZNeUPGFe/eQHsPWkVXWZX mRN/PoWGFK+sJBLihvoTOMVRqxuBu2Xfan4nrYKTt9mw5giyZ093HzA1s0pyIGUMvaRhPFiZl/1XR jy69gJCg==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1xBdDX-00000004LoE-0k03; Tue, 29 Sep 2026 19:10:19 +0000 Received: from foss.arm.com ([217.140.110.172]) by bombadil.infradead.org with esmtp (Exim 4.99.1 #2 (Red Hat Linux)) id 1xBdDU-00000004Lnp-1Ker for linux-arm-kernel@lists.infradead.org; Tue, 29 Sep 2026 19:10:17 +0000 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 08B9C1516; Tue, 29 Sep 2026 12:10:11 -0700 (PDT) Received: from e129823.arm.com (e129823.arm.com [10.2.213.3]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id C8AFE3F763; Tue, 29 Sep 2026 12:10:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=arm.com; s=foss; t=1790709014; bh=NOIA0AhIJOaacWDtLcFjg4c7jFIJA0gynFswtjRKP4I=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=N1hUaKNiEPIGTdjn89BresTbDyQqvAZsh6KjBH1BX8GhcBrLkxlS9vDKSEPAmkKM3 0tsnYty7LGAf/vqgRtt9e6bjqrbT6wBSzT+nnmoRN5ek7oGygi7thl/IDZUda9oj2s lwR9mekKjb7xkJVw7tT8cQUDtADrKOETIWPEmQT0= Date: Tue, 29 Sep 2026 20:10:09 +0100 From: Yeoreum Yun To: Jason Gunthorpe Cc: Yeoreum Yun , Jiri Pirko , Sami Mujawar , Suzuki Poulose , Dan Williams , "linux-arm-kernel@lists.infradead.org" , "linux-kernel@vger.kernel.org" , Catalin Marinas , "will@kernel.org" , "thuth@redhat.com" , Steven Price , "gshan@redhat.com" , "cedric.xing@intel.com" , Dionna Glaze , "Aneesh Kumar K . V" , Alexey Kardashevskiy , "linux-coco@lists.linux.dev" Subject: Re: [PATCH 0/3] arm64/virt: Add Arm CCA measurement register support Message-ID: References: <20260413084957.327661-1-sami.mujawar@arm.com> <20260413125925.GK3694781@ziepe.ca> <514ddb27-137b-4223-84fe-2152737db3a6@arm.com> <20260414122950.GW3694781@ziepe.ca> <20260414133525.GA2577880@ziepe.ca> <20260422124041.GJ3611611@ziepe.ca> <20260929190450.GM163130@ziepe.ca> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20260929190450.GM163130@ziepe.ca> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.9.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20260929_121016_509495_D2E41B92 X-CRM114-Status: GOOD ( 25.31 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Tue, Sep 29, 2026 at 04:04:50PM -0300, Jason Gunthorpe wrote: > On Tue, Sep 29, 2026 at 05:06:02PM +0100, Yeoreum Yun wrote: > > Hi Jason, > > > > > On Wed, Apr 22, 2026 at 08:57:00AM +0000, Sami Mujawar wrote: > > > > > > > > So this is tying it to the same FW event log that TPM uses. > > > > > > > > > > I think that strengthens my point this should all be uninform. TPM > > > > > drivers are directly exposing the event log today, but I guess that > > > > > needs generalization if non-TPM drivers are going to present it as > > > > > well. > > > > > > > > > > How do you imagine getting and manipulating the EFI event log to use > > > > > with this? > > > > > > > > The event logs from UEFI will be handed off to the OS using CCEL > > > > ACPI table. The CCEL table spec update can be seen at > > > > https://github.com/tianocore/edk2/issues/11384 > > > > > > I ment from linux userspace. event log is well establihsed in the aCPI > > > side for TPM and in Linux today it is only exposed to userspace > > > through TPM. > > > > > > This is not TPM, so how do you intend to give the event log to > > > userspace? > > > > The event log would be exported via /sys/firmware/acpi/tables/data/CCEL > > with binary format just as TPM event log is also exported with binary > > format via binary_bios_measurements. > > > > Instead of Sami, I'll post v2 which rebased on for-next/smccc-bus in > > arm64 tree. > > Okay, Jiri is close to posting the "attestation subsystem" which this > needs to plug into instead of creating a bunch more sysfs files. > > The CCEL log needs to come out through that interface. Agree. Thanks for sharing! -- Sincerely, Yeoreum Yun