From: Dan Williams <dan.j.williams@intel.com>
To: "Kirill A. Shutemov" <kirill.shutemov@linux.intel.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: <linux-coco@lists.linux.dev>, Kai Huang <kai.huang@intel.com>,
Dave Hansen <dave.hansen@linux.intel.com>, <x86@kernel.org>,
<aik@amd.com>, <elena.reshetova@intel.com>, <pgonda@google.com>
Subject: Re: [PATCH 3/4] x86/tdx: Introduce guest global metadata retrieval infrastructure
Date: Tue, 1 Oct 2024 00:56:51 -0700 [thread overview]
Message-ID: <66fbab43963ad_964f229422@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <fg4oibulhylpceczrts2wt4d6cbvfwnyu2gnji63u3hx43eeks@ksdkcowisam3>
Kirill A. Shutemov wrote:
> On Thu, Sep 12, 2024 at 05:26:18PM -0700, Dan Williams wrote:
> > Similar to the host side [1], build some macro helpers for retrieving
> > global metadata fields.
> >
> > This infrastructure is overkill if the guest only ends up consuming a
> > few fields of metadata. Some of the overhead reduced later by
> > refactoring the TDH_SYS_RD (host side) infrastructure to optionally
> > support TDG_SYS_RD (guest side) as an alternate low-level transport.
> >
> > If this moves forward, expect that it is rebased on the host side
> > metadata patches to share infrastructure.
>
> This patchset already introduces helper for TDG_VM_RD. The same can be
> done for TDG_SYS_RD.
>
> https://lore.kernel.org/all/20240828093505.2359947-1-kirill.shutemov@linux.intel.com/
Shouldn't this be reworked to use the same metadata reading
infrastructure as Kai is introducing for the host side?
http://lore.kernel.org/1b14e28b-972e-4277-898f-8e2dcb77e144@intel.com
next prev parent reply other threads:[~2024-10-01 7:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-13 0:25 [PATCH 0/4] configfs-tsm-report: TCB Stability Dan Williams
2024-09-13 0:26 ` [PATCH 1/4] configfs-tsm: Namespace TSM report symbols Dan Williams
2024-09-13 0:26 ` [PATCH 2/4] coco/guest: Move shared guest CC infrastructure to drivers/virt/coco/guest/ Dan Williams
2024-09-13 0:26 ` [PATCH 3/4] x86/tdx: Introduce guest global metadata retrieval infrastructure Dan Williams
2024-09-16 8:56 ` Kirill A. Shutemov
2024-10-01 7:56 ` Dan Williams [this message]
2024-09-13 0:26 ` [PATCH 4/4] configfs-tsm-report: Introduce TCB stability enumeration and watchdog Dan Williams
2024-09-16 9:06 ` Kirill A. Shutemov
2024-10-01 0:33 ` Dan Williams
2024-10-01 8:50 ` Alexander Graf
2024-10-04 21:36 ` Dan Williams
2024-10-07 8:33 ` Alexander Graf
2024-10-07 18:22 ` Dave Hansen
2024-10-07 18:59 ` Dan Williams
2024-10-07 19:43 ` Dionna Amalie Glaze
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=66fbab43963ad_964f229422@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=aik@amd.com \
--cc=dave.hansen@linux.intel.com \
--cc=elena.reshetova@intel.com \
--cc=kai.huang@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=linux-coco@lists.linux.dev \
--cc=pgonda@google.com \
--cc=x86@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