From: Jason Gunthorpe <jgg@ziepe.ca>
To: Suzuki K Poulose <suzuki.poulose@arm.com>
Cc: Sami Mujawar <sami.mujawar@arm.com>,
Dan Williams <djbw@kernel.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, catalin.marinas@arm.com,
will@kernel.org, thuth@redhat.com, steven.price@arm.com,
gshan@redhat.com, YeoReum.Yun@arm.com, cedric.xing@intel.com,
Dan Williams <dan.j.williams@intel.com>,
Dionna Glaze <dionnaglaze@google.com>,
"Aneesh Kumar K . V" <aneesh.kumar@kernel.org>,
Alexey Kardashevskiy <aik@amd.com>,
"linux-coco@lists.linux.dev" <linux-coco@lists.linux.dev>
Subject: Re: [PATCH 0/3] arm64/virt: Add Arm CCA measurement register support
Date: Tue, 14 Apr 2026 09:29:50 -0300 [thread overview]
Message-ID: <20260414122950.GW3694781@ziepe.ca> (raw)
In-Reply-To: <514ddb27-137b-4223-84fe-2152737db3a6@arm.com>
On Tue, Apr 14, 2026 at 11:10:51AM +0100, Suzuki K Poulose wrote:
> > Isn't this also sort of incomplete? Doesn't anything serious need
> > signed measurements? Isnt't there alot more data that comes out of RMM
> > than just a few measurement registers?
> As mentioned above, this series adds the support for Runtime Extendible
> Measurements (REM in CCA, RTMR on TDX). The RIM+Platform Attestation is
> already provided via the TSM_REPORT
Okay, but what actual use is this?
Extendable measrements with no log
Measurement read back without signature
What is the use case? What do you imagine any userspace will do with
this? Put it in the cover letter.
I don't think the raw rmm calls are sufficiently developed to be
usable directly by userspace. They are less capable than TPM and even
TPM has a lot of software around it to make it useful.
Jason
next prev parent reply other threads:[~2026-04-14 12:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20260413084957.327661-1-sami.mujawar@arm.com>
[not found] ` <20260413125925.GK3694781@ziepe.ca>
2026-04-14 10:10 ` [PATCH 0/3] arm64/virt: Add Arm CCA measurement register support Suzuki K Poulose
2026-04-14 12:29 ` Jason Gunthorpe [this message]
2026-04-14 13:26 ` Suzuki K Poulose
2026-04-14 13:35 ` Jason Gunthorpe
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260414122950.GW3694781@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=YeoReum.Yun@arm.com \
--cc=aik@amd.com \
--cc=aneesh.kumar@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=cedric.xing@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dionnaglaze@google.com \
--cc=djbw@kernel.org \
--cc=gshan@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=sami.mujawar@arm.com \
--cc=steven.price@arm.com \
--cc=suzuki.poulose@arm.com \
--cc=thuth@redhat.com \
--cc=will@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox