[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <39c0a7dd85b3385b21ce53d9d7d31301bbbc5ac4.camel@intel.com>
Date: Mon, 12 Sep 2022 21:01:43 +0000
From: "Huang, Kai" <kai.huang@...el.com>
To: "sathyanarayanan.kuppuswamy@...ux.intel.com"
<sathyanarayanan.kuppuswamy@...ux.intel.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"mingo@...hat.com" <mingo@...hat.com>,
"shuah@...nel.org" <shuah@...nel.org>,
"dave.hansen@...ux.intel.com" <dave.hansen@...ux.intel.com>,
"x86@...nel.org" <x86@...nel.org>, "bp@...en8.de" <bp@...en8.de>
CC: "linux-kselftest@...r.kernel.org" <linux-kselftest@...r.kernel.org>,
"ak@...ux.intel.com" <ak@...ux.intel.com>,
"gregkh@...uxfoundation.org" <gregkh@...uxfoundation.org>,
"wander@...hat.com" <wander@...hat.com>,
"tim.gardner@...onical.com" <tim.gardner@...onical.com>,
"hpa@...or.com" <hpa@...or.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"isaku.yamahata@...il.com" <isaku.yamahata@...il.com>,
"kirill.shutemov@...ux.intel.com" <kirill.shutemov@...ux.intel.com>,
"Luck, Tony" <tony.luck@...el.com>,
"marcelo.cerri@...onical.com" <marcelo.cerri@...onical.com>,
"Cox, Philip" <philip.cox@...onical.com>,
"khalid.elmously@...onical.com" <khalid.elmously@...onical.com>,
"linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>
Subject: Re: [PATCH v13 3/3] Documentation/x86: Document TDX attestation
process
On Mon, 2022-09-12 at 07:15 -0700, Sathyanarayanan Kuppuswamy wrote:
>
> On 9/12/22 12:04 AM, Huang, Kai wrote:
> > > +
> > > +TDX Guest driver
> > > +================
> > > +
> > > +The TDX guest driver exposes IOCTL interfaces via /dev/tdx-guest misc
> > > +device to allow user space to get certain TDX guest specific details
> > > +(like attestation report, attestation quote or storage keys, etc).
> > Only TDX_CMD_GET_REPORT is supported now. Whether GetQuote TDVMCALL should be
> > supported, or how should it be supported is unknown now. Not to mention "get
> > the storage keys".
>
> The reason for adding them is to give an idea that this driver in future could
> be used for use cases other than GetReport. Query about possible use cases came up
> in a previous review about /dev/tdx-guest device name usage. So I thought it is
> better to give a clear idea on how this device may be used in the future.
But I don't think "attestation quote or storage keys" are good example, as it's
uncertain, i.e. can be wrong to put here.
>
> Maybe I can add a note that currently only attestation report is supported.
Maybe something like this?
"
The TDX guest exposes /dev/tdx-guest to userspace to support all TDX guest
specific operations in one driver. Currently only TDX_CMD_GET_RERPORT IOCTL is
supported to return the TDREPORT to userspace to support attestation for the TDX
guest.
"
--
Thanks,
-Kai
Powered by blists - more mailing lists