From: Dan Williams <dan.j.williams@intel.com>
To: "Xing, Cedric" <cedric.xing@intel.com>,
Jean-Philippe Brucker <jean-philippe@linaro.org>
Cc: Dan Williams <dan.j.williams@intel.com>,
Samuel Ortiz <sameo@rivosinc.com>,
James Bottomley <James.Bottomley@hansenpartnership.com>,
Lukas Wunner <lukas@wunner.de>,
Dionna Amalie Glaze <dionnaglaze@google.com>,
Qinkun Bao <qinkun@google.com>,
Mikko Ylinen <mikko.ylinen@linux.intel.com>,
Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
<linux-kernel@vger.kernel.org>, <linux-coco@lists.linux.dev>,
<suzuki.poulose@arm.com>, <sami.mujawar@arm.com>
Subject: Re: [PATCH RFC 0/3] tsm: Unified Measurement Register ABI for TVMs
Date: Wed, 11 Sep 2024 16:36:46 -0700 [thread overview]
Message-ID: <66e2298eb64ec_3263b2945@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <f6b0a1d2-c730-4b20-a8f3-afd9a7cf822a@intel.com>
Xing, Cedric wrote:
[..]
> With regard to the location of the MR tree, we picked sysfs because the
> MRs (and associated logs) are global and fit more into the semantics of
> sysfs than configfs. Dan W. and I are also considering moving both
> report/ and measurement/ trees into securityfs. It'll be highly
> appreciated if you (and Alex, and everyone) can share your insights.
I would only expect this new measurement interface is suitable for
considering securityfs. The tsm_report uAPI is already baked and has a
need for the multi-instance support of configfs.
The rationale for RTMR measurements in securityfs is because the IMA
measurement uAPI already lives there. So it is more about following
precedent for co-locating a new ASCII RTMR measurement log in the same
filesystem that provides ima/ascii_runtime_measurements.
A multi-instance interface for virtual RTMRs might be suitable to live
in configfs alongside reports/, and use this native singleton log as a
backend.
next prev parent reply other threads:[~2024-09-11 23:36 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-08 4:56 [PATCH RFC 0/3] tsm: Unified Measurement Register ABI for TVMs Cedric Xing
2024-09-08 4:56 ` [PATCH RFC 1/3] tsm: Add TVM Measurement Register Support Cedric Xing
2024-09-08 4:56 ` [PATCH RFC 2/3] tsm: Add RTMR event logging Cedric Xing
2024-09-08 4:56 ` [PATCH RFC 3/3] tsm: Add TVM Measurement Sample Code Cedric Xing
2024-09-09 15:14 ` Jeff Johnson
2024-09-09 15:20 ` Xing, Cedric
2024-09-12 12:28 ` James Bottomley
2024-09-14 16:36 ` Xing, Cedric
2024-09-14 17:10 ` James Bottomley
2024-09-15 4:53 ` Xing, Cedric
2024-10-24 17:21 ` Mikko Ylinen
2024-09-08 17:37 ` [PATCH RFC 0/3] tsm: Unified Measurement Register ABI for TVMs Alexander Graf
2024-09-09 14:55 ` Xing, Cedric
2024-09-10 7:47 ` Alexander Graf
2024-09-10 18:07 ` Xing, Cedric
2024-09-10 17:09 ` Jean-Philippe Brucker
2024-09-11 4:01 ` Xing, Cedric
2024-09-11 6:56 ` Alexander Graf
2024-09-12 15:43 ` Xing, Cedric
2024-09-13 9:43 ` Alexander Graf
2024-09-11 12:06 ` James Bottomley
2024-09-11 13:46 ` Qinkun Bao
2024-09-11 14:10 ` James Bottomley
2024-09-12 3:23 ` Xing, Cedric
2024-09-12 12:15 ` James Bottomley
2024-09-12 19:00 ` Xing, Cedric
2024-09-13 12:55 ` James Bottomley
2024-09-15 4:31 ` Xing, Cedric
2024-09-13 12:58 ` James Bottomley
2024-09-15 5:14 ` Xing, Cedric
2024-09-11 23:29 ` Dan Williams
2024-09-11 23:36 ` Dan Williams [this message]
2024-09-12 9:25 ` Jean-Philippe Brucker
2024-09-12 10:03 ` Christophe de Dinechin
2024-09-12 11:02 ` Jean-Philippe Brucker
2024-09-13 19:42 ` Xing, Cedric
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=66e2298eb64ec_3263b2945@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=James.Bottomley@hansenpartnership.com \
--cc=cedric.xing@intel.com \
--cc=dionnaglaze@google.com \
--cc=jean-philippe@linaro.org \
--cc=linux-coco@lists.linux.dev \
--cc=linux-kernel@vger.kernel.org \
--cc=lukas@wunner.de \
--cc=mikko.ylinen@linux.intel.com \
--cc=qinkun@google.com \
--cc=sameo@rivosinc.com \
--cc=sami.mujawar@arm.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.com \
--cc=suzuki.poulose@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).