From: Jason Gunthorpe <jgg@ziepe.ca>
To: Yeoreum Yun <yeoreum.yun@arm.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
Catalin Marinas <catalin.marinas@arm.com>,
Will Deacon <will@kernel.org>,
Suzuki Poulose <suzuki.poulose@arm.com>,
Steven Price <steven.price@arm.com>,
Sami Mujawar <sami.mujawar@arm.com>,
thuth@redhat.com, Jiri Pirko <jiri@nvidia.com>
Subject: Re: [PATCH v2 0/3] arm64/virt: Add Arm CCA measurement register support
Date: Tue, 29 Sep 2026 16:45:01 -0300 [thread overview]
Message-ID: <20260929194501.GO163130@ziepe.ca> (raw)
In-Reply-To: <arwUrOYn0NVySdzm@e129823.arm.com>
On Tue, Sep 29, 2026 at 08:42:36PM +0100, Yeoreum Yun wrote:
> On Tue, Sep 29, 2026 at 04:20:51PM -0300, Jason Gunthorpe wrote:
> > On Tue, Sep 29, 2026 at 05:57:46PM +0100, Yeoreum Yun wrote:
> > > This series adds support for Arm Confidential Compute Architecture (CCA)
> > > measurement registers in the Linux kernel, enabling guest Realms to
> > > access, extend, and expose measurement values for attestation and runtime
> > > integrity tracking.
> >
> > I'd prefer not to add any more tsm_measurements users until we bottom
> > out on the attestation subsystem.. Mainly because it establishes uAPI
> > that doesn't really do everything people need from this stuff..
>
> Tend to agree. However, I think this seems like an integration with
> the attestation subsystem.
> IOW, although the functionality and interface are currently scattered,
> the functionality of the TSM MR doesn't change —
> showing the current measurement register status and generating
> a token with a challenge. Therefore, even if the subsystem is refactored,
> I don't think this would be a burden for it, and personally,
> I'd like to see this patch series emancipated from almost six months of waiting ;)
Yeah, but it immediately establishes a sysfs uAPI that we don't want
anyone to implement :( That's my main issue..
Jason
prev parent reply other threads:[~2026-09-29 19:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 16:57 [PATCH v2 0/3] arm64/virt: Add Arm CCA measurement register support Yeoreum Yun
2026-09-29 16:57 ` [PATCH v2 1/3] arm64: rsi: Add helpers for Arm CCA measurement register operations Yeoreum Yun
2026-09-30 2:04 ` Kohei Enju
2026-09-30 5:13 ` Yeoreum Yun
2026-09-29 16:57 ` [PATCH v2 2/3] arm64: rsi: Add realm hash algorithm defines Yeoreum Yun
2026-09-30 2:39 ` Kohei Enju
2026-09-30 5:10 ` Yeoreum Yun
2026-09-29 16:57 ` [PATCH v2 3/3] virt: arm-cca-guest: Add support for measurement registers Yeoreum Yun
2026-09-30 3:24 ` Kohei Enju
2026-09-30 4:45 ` Kohei Enju
2026-09-30 5:09 ` Yeoreum Yun
2026-09-30 5:59 ` Kohei Enju
2026-09-30 6:40 ` Yeoreum Yun
2026-09-30 7:04 ` Kohei Enju
2026-09-30 7:54 ` Yeoreum Yun
2026-09-30 13:54 ` Jason Gunthorpe
2026-09-30 14:12 ` Yeoreum Yun
2026-09-30 14:17 ` Jason Gunthorpe
2026-09-30 14:28 ` Yeoreum Yun
2026-10-01 1:33 ` Kohei Enju
2026-09-29 19:20 ` [PATCH v2 0/3] arm64/virt: Add Arm CCA measurement register support Jason Gunthorpe
2026-09-29 19:42 ` Yeoreum Yun
2026-09-29 19:45 ` Jason Gunthorpe [this message]
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=20260929194501.GO163130@ziepe.ca \
--to=jgg@ziepe.ca \
--cc=catalin.marinas@arm.com \
--cc=jiri@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--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 \
--cc=yeoreum.yun@arm.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.