From: Sergii Dmytruk <sergii.dmytruk@3mdeb.com>
To: ross.philipson@oracle.com
Cc: xen-devel@lists.xenproject.org,
"Andrew Cooper" <andrew.cooper3@citrix.com>,
"Anthony PERARD" <anthony.perard@vates.tech>,
"Michal Orzel" <michal.orzel@amd.com>,
"Jan Beulich" <jbeulich@suse.com>,
"Julien Grall" <julien@xen.org>,
"Roger Pau Monné" <roger.pau@citrix.com>,
"Stefano Stabellini" <sstabellini@kernel.org>,
trenchboot-devel@googlegroups.com
Subject: Re: [PATCH 02/21] include/xen/slr_table.h: Secure Launch Resource Table definitions
Date: Wed, 23 Apr 2025 17:47:52 +0300 [thread overview]
Message-ID: <aAj9mO3btAWZbOJp@MjU3Nj> (raw)
In-Reply-To: <87ad3627-088c-442b-bc2b-89586a082599@oracle.com>
On Tue, Apr 22, 2025 at 01:46:14PM -0700, ross.philipson@oracle.com wrote:
> > +
> > +/*
> > + * ARM DRTM Info table
> > + */
> > +struct slr_entry_arm_info
> > +{
> > + struct slr_entry_hdr hdr;
> > +} __packed;
>
> You can probably ditch this for now.
Right, it has no value at this point.
> I am surprised you did not need the slr_add_entry() function. How do you add
> entries to the SLRT?
Xen doesn't add any SLRT entries. It's also the final consumer of the
SLRT, at least at the moment, so no need to update something that won't
be used again.
> Thanks
> Ross
next prev parent reply other threads:[~2025-04-23 14:48 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 15:06 [PATCH 00/21] x86: Trenchboot Secure Launch DRTM (Xen) Sergii Dmytruk
2025-04-22 15:06 ` [PATCH 01/21] x86/include/asm/intel_txt.h: constants and accessors for TXT registers and heap Sergii Dmytruk
2025-04-22 15:06 ` [PATCH 02/21] include/xen/slr_table.h: Secure Launch Resource Table definitions Sergii Dmytruk
2025-04-22 20:23 ` Andrew Cooper
2025-04-23 14:40 ` Sergii Dmytruk
2025-04-22 20:46 ` ross.philipson
2025-04-23 14:47 ` Sergii Dmytruk [this message]
2025-04-23 17:33 ` ross.philipson
2025-04-22 15:06 ` [PATCH 03/21] x86/boot: add MLE header and new entry point Sergii Dmytruk
2025-04-22 15:06 ` [PATCH 04/21] x86/boot/slaunch_early: implement early initialization Sergii Dmytruk
2025-04-22 15:06 ` [PATCH 05/21] x86/boot/slaunch_early: early TXT checks and boot data retrieval Sergii Dmytruk
2025-04-22 15:06 ` [PATCH 06/21] xen/arch/x86: reserve TXT memory Sergii Dmytruk
2025-04-22 15:06 ` [PATCH 07/21] x86/mtrr: expose functions for pausing caching Sergii Dmytruk
2025-04-22 15:06 ` [PATCH 08/21] x86/intel_txt.c: restore boot MTRRs Sergii Dmytruk
2025-04-22 15:06 ` [PATCH 09/21] lib/sha1.c: add file Sergii Dmytruk
2025-04-22 15:36 ` Jan Beulich
2025-04-22 22:15 ` Sergii Dmytruk
2025-04-22 15:06 ` [PATCH 10/21] lib/sha256.c: " Sergii Dmytruk
2025-04-22 15:37 ` Andrew Cooper
2025-04-22 22:20 ` Sergii Dmytruk
2025-04-22 15:39 ` Jan Beulich
2025-04-22 15:06 ` [PATCH 11/21] x86/tpm.c: code for early hashing and extending PCRs (for TPM1.2) Sergii Dmytruk
2025-04-22 15:06 ` [PATCH 12/21] x86/tpm.c: support extending PCRs of TPM2.0 Sergii Dmytruk
2025-04-22 15:06 ` [PATCH 13/21] x86/hvm: Check for VMX in SMX when slaunch active Sergii Dmytruk
2025-04-22 15:06 ` [PATCH 14/21] x86/tpm.c: implement event log for TPM2.0 Sergii Dmytruk
2025-04-22 15:06 ` [PATCH 15/21] x86/boot: choose AP stack based on APIC ID Sergii Dmytruk
2025-04-22 15:06 ` [PATCH 16/21] x86/smpboot.c: TXT AP bringup Sergii Dmytruk
2025-04-22 15:06 ` [PATCH 17/21] arch/x86: process DRTM policy Sergii Dmytruk
2025-04-22 15:06 ` [PATCH 18/21] x86/boot: find MBI and SLRT on AMD Sergii Dmytruk
2025-04-22 15:06 ` [PATCH 19/21] arch/x86: support slaunch with AMD SKINIT Sergii Dmytruk
2025-04-22 15:06 ` [PATCH 20/21] x86/slaunch: support EFI boot Sergii Dmytruk
2025-04-22 15:06 ` [PATCH 21/21] x86/cpu: report SMX, TXT and SKINIT capabilities Sergii Dmytruk
2025-04-22 15:23 ` [PATCH 00/21] x86: Trenchboot Secure Launch DRTM (Xen) Jan Beulich
2025-04-22 18:33 ` Sergii Dmytruk
2025-04-22 17:14 ` Andrew Cooper
2025-04-22 19:01 ` Nicola Vetrini
2025-04-23 13:38 ` Andrew Cooper
2025-04-23 18:45 ` Sergii Dmytruk
2025-04-23 20:11 ` Nicola Vetrini
2025-04-23 21:53 ` Sergii Dmytruk
2025-04-24 10:54 ` Nicola Vetrini
2025-04-24 18:14 ` Sergii Dmytruk
2025-04-23 22:43 ` Andrew Cooper
2025-04-24 18:47 ` Sergii Dmytruk
2025-04-24 18:51 ` Andrew Cooper
2025-04-25 13:33 ` Sergii Dmytruk
2025-04-23 18:59 ` Daniel P. Smith
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=aAj9mO3btAWZbOJp@MjU3Nj \
--to=sergii.dmytruk@3mdeb.com \
--cc=andrew.cooper3@citrix.com \
--cc=anthony.perard@vates.tech \
--cc=jbeulich@suse.com \
--cc=julien@xen.org \
--cc=michal.orzel@amd.com \
--cc=roger.pau@citrix.com \
--cc=ross.philipson@oracle.com \
--cc=sstabellini@kernel.org \
--cc=trenchboot-devel@googlegroups.com \
--cc=xen-devel@lists.xenproject.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 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.