From: Dan Williams <dan.j.williams@intel.com>
To: Dan Middleton <dan.middleton@linux.intel.com>,
Mikko Ylinen <mikko.ylinen@linux.intel.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: Kuppuswamy Sathyanarayanan
<sathyanarayanan.kuppuswamy@linux.intel.com>,
Nikolay Borisov <nik.borisov@suse.com>,
<linux-coco@lists.linux.dev>, <x86@kernel.org>,
<dave.hansen@linux.intel.com>, <dionnaglaze@google.com>
Subject: Re: [PATCH] virt: tdx-guest: Deprecate legacy IOCTL-based interface for quote generation
Date: Mon, 12 Feb 2024 15:12:09 -0800 [thread overview]
Message-ID: <65caa5c94f06b_5a7f294ed@dwillia2-xfh.jf.intel.com.notmuch> (raw)
In-Reply-To: <bb5543c8-b14e-42cb-a13b-9467fa87622f@linux.intel.com>
Dan Middleton wrote:
[..]
> I would suspect that other vendors will offer local attestations based
> on local appearing in SGX and TDX, but that's speculation. If so their
> APIs would better inform a new common configfs-tsm feature.
> Maybe people with knowledge of AMD, Arm, and RISC-V disclosed plans can
> comment.
FWIW, I am looking at resolution of this proposal [1] as providing the
configfs-tsm infrastructure to trigger the deprecation of the tdx-guest
report ioctl(). I.e. once configfs-tsm generically supports local
attestation flows then software has a migration path.
Comments from folks on this thread welcome over there [1].
[1]: http://lore.kernel.org/r/cover.1706307364.git.thomas.lendacky@amd.com
next prev parent reply other threads:[~2024-02-12 23:12 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-24 9:38 [PATCH] virt: tdx-guest: Deprecate legacy IOCTL-based interface for quote generation Nikolay Borisov
2024-01-31 7:28 ` Nikolay Borisov
2024-01-31 15:27 ` Dave Hansen
2024-01-31 18:18 ` Nikolay Borisov
2024-01-31 19:05 ` Dave Hansen
2024-02-01 4:14 ` Haitao Huang
2024-02-01 4:55 ` Dan Williams
2024-01-31 7:48 ` Kuppuswamy Sathyanarayanan
2024-01-31 19:50 ` Dan Williams
2024-01-31 19:56 ` Nikolay Borisov
2024-01-31 20:44 ` Kuppuswamy Sathyanarayanan
2024-01-31 21:00 ` Daniel P. Berrangé
2024-01-31 21:12 ` Dan Williams
2024-02-01 2:52 ` Kuppuswamy Sathyanarayanan
2024-02-01 8:15 ` Daniel P. Berrangé
2024-01-31 21:09 ` Dan Williams
2024-02-08 13:42 ` Mikko Ylinen
2024-02-09 2:23 ` Dan Middleton
2024-02-12 23:12 ` Dan Williams [this message]
2024-01-31 20:23 ` Dan Williams
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=65caa5c94f06b_5a7f294ed@dwillia2-xfh.jf.intel.com.notmuch \
--to=dan.j.williams@intel.com \
--cc=dan.middleton@linux.intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dionnaglaze@google.com \
--cc=linux-coco@lists.linux.dev \
--cc=mikko.ylinen@linux.intel.com \
--cc=nik.borisov@suse.com \
--cc=sathyanarayanan.kuppuswamy@linux.intel.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;
as well as URLs for NNTP newsgroup(s).