lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Thu, 18 Aug 2022 09:33:23 +0000 From: "Huang, Kai" <kai.huang@...el.com> To: "bagasdotme@...il.com" <bagasdotme@...il.com> CC: "kvm@...r.kernel.org" <kvm@...r.kernel.org>, "Hansen, Dave" <dave.hansen@...el.com>, "Luck, Tony" <tony.luck@...el.com>, "ak@...ux.intel.com" <ak@...ux.intel.com>, "Wysocki, Rafael J" <rafael.j.wysocki@...el.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "Christopherson,, Sean" <seanjc@...gle.com>, "Chatre, Reinette" <reinette.chatre@...el.com>, "pbonzini@...hat.com" <pbonzini@...hat.com>, "Yamahata, Isaku" <isaku.yamahata@...el.com>, "kirill.shutemov@...ux.intel.com" <kirill.shutemov@...ux.intel.com>, "linux-doc@...r.kernel.org" <linux-doc@...r.kernel.org>, "peterz@...radead.org" <peterz@...radead.org>, "Brown, Len" <len.brown@...el.com>, "sathyanarayanan.kuppuswamy@...ux.intel.com" <sathyanarayanan.kuppuswamy@...ux.intel.com>, "Williams, Dan J" <dan.j.williams@...el.com> Subject: Re: [PATCH v5 22/22] Documentation/x86: Add documentation for TDX host support On Thu, 2022-08-18 at 11:07 +0700, Bagas Sanjaya wrote: > On Wed, Jun 22, 2022 at 11:17:50PM +1200, Kai Huang wrote: > > +Kernel detects TDX and the TDX private KeyIDs during kernel boot. User > > +can see below dmesg if TDX is enabled by BIOS: > > + > > +| [..] tdx: SEAMRR enabled. > > +| [..] tdx: TDX private KeyID range: [16, 64). > > +| [..] tdx: TDX enabled by BIOS. > > + > <snipped> > > +Initializing the TDX module consumes roughly ~1/256th system RAM size to > > +use it as 'metadata' for the TDX memory. It also takes additional CPU > > +time to initialize those metadata along with the TDX module itself. Both > > +are not trivial. Current kernel doesn't choose to always initialize the > > +TDX module during kernel boot, but provides a function tdx_init() to > > +allow the caller to initialize TDX when it truly wants to use TDX: > > + > > + ret = tdx_init(); > > + if (ret) > > + goto no_tdx; > > + // TDX is ready to use > > + > > Hi, > > The code block above produces Sphinx warnings: > > Documentation/x86/tdx.rst:69: WARNING: Unexpected indentation. > Documentation/x86/tdx.rst:70: WARNING: Block quote ends without a blank line; unexpected unindent. > > I have applied the fixup: > Thank you! will fix in next version. -- Thanks, -Kai
Powered by blists - more mailing lists