A gentle ping on this email thread. We have tested the patch series [1] and will release a product based on the patch series. If the patch series can not get upstreamed, the whole confidential computing community can not have a way to measure the workload with RTMRs. Without the patch, RTMR3 is completely unused. The patch works perfectly for our usage case (Like the existing TPM ABI, the raw measurement is taken instead of recording the log entry.). Assuming RTMR serves as an alternative to TPM-based measurement, migrating existing software to the RTMR could be greatly simplified by developing an ABI that resembles the TPM. I don’t object to having an ABI to take the log entry. For our usage case, we use the Canonical event log [2] to measure the workload. I do think that we should NOT block the patch series for several months to solve an issue that TPM can not solve. Link: [1] https://lore.kernel.org/lkml/20240128212532.2754325-1-sameo@xxxxxxxxxxxx/ [2] https://trustedcomputinggroup.org/resource/canonical-event-log-format/
