[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <283b3d47-f1f6-3c53-0909-ba0540993203@intel.com>
Date: Thu, 20 May 2021 14:23:27 -0700
From: Dave Hansen <dave.hansen@...el.com>
To: Sean Christopherson <seanjc@...gle.com>,
Andi Kleen <ak@...ux.intel.com>
Cc: "Kuppuswamy, Sathyanarayanan"
<sathyanarayanan.kuppuswamy@...ux.intel.com>,
Peter Zijlstra <peterz@...radead.org>,
Andy Lutomirski <luto@...nel.org>,
Dan Williams <dan.j.williams@...el.com>,
Tony Luck <tony.luck@...el.com>,
Kirill Shutemov <kirill.shutemov@...ux.intel.com>,
Kuppuswamy Sathyanarayanan <knsathya@...nel.org>,
Raj Ashok <ashok.raj@...el.com>, linux-kernel@...r.kernel.org
Subject: Re: [RFC v2 27/32] x86/tdx: Exclude Shared bit from __PHYSICAL_MASK
On 5/20/21 2:18 PM, Sean Christopherson wrote:
> I understand the desire to have a unique prefix, but tdg is is _too_ close to
> tdx. I don't want to spend the next N years wondering if tdg is a typo or intended.
Sathya has even mis-typed "tdx" instead of "tdg" this in his own
changelogs up to this point. That massively weakens the argument that
"tdg" is a good idea.
Powered by blists - more mailing lists