[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 3 Apr 2022 23:25:23 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Kai Huang <kai.huang@...el.com>,
"Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>,
tglx@...utronix.de, mingo@...hat.com, bp@...en8.de,
luto@...nel.org, peterz@...radead.org
Cc: sathyanarayanan.kuppuswamy@...ux.intel.com, aarcange@...hat.com,
ak@...ux.intel.com, dan.j.williams@...el.com, david@...hat.com,
hpa@...or.com, jgross@...e.com, jmattson@...gle.com,
joro@...tes.org, jpoimboe@...hat.com, knsathya@...nel.org,
pbonzini@...hat.com, sdeep@...are.com, seanjc@...gle.com,
tony.luck@...el.com, vkuznets@...hat.com, wanpengli@...cent.com,
thomas.lendacky@....com, brijesh.singh@....com, x86@...nel.org,
linux-kernel@...r.kernel.org,
Dave Hansen <dave.hansen@...ux.intel.com>
Subject: Re: [PATCHv7 30/30] Documentation/x86: Document TDX kernel
architecture
On 4/3/22 21:32, Kai Huang wrote:
> This is not the best way I believe. I think we have two options here:
> 1) Having dedicated tdx_guest.rst and tdx_host.rst
> 2) Having a single tdx.rst to cover both TDX guest and host materials.
>
> I don't know which way is better, perhaps 2).
>
> Kirill,
>
> If 2) is better, could we add an additional level of menu to represent "TDX
> guest support" and make all materials as sub-menu of it, if you need to send out
> v8?
If the host support means that this needs to be reorganized, then the
host support patches can do that. Let's not make this more complicated
than it has to be.
Powered by blists - more mailing lists