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: Wed, 14 Sep 2022 09:25:45 -0700 From: Sathyanarayanan Kuppuswamy <sathyanarayanan.kuppuswamy@...ux.intel.com> To: Dave Hansen <dave.hansen@...el.com>, Thomas Gleixner <tglx@...utronix.de>, Ingo Molnar <mingo@...hat.com>, Borislav Petkov <bp@...en8.de>, Dave Hansen <dave.hansen@...ux.intel.com>, x86@...nel.org, Shuah Khan <shuah@...nel.org> Cc: "H . Peter Anvin" <hpa@...or.com>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, "Kirill A . Shutemov" <kirill.shutemov@...ux.intel.com>, Tony Luck <tony.luck@...el.com>, Andi Kleen <ak@...ux.intel.com>, Kai Huang <kai.huang@...el.com>, Wander Lairson Costa <wander@...hat.com>, Isaku Yamahata <isaku.yamahata@...il.com>, marcelo.cerri@...onical.com, tim.gardner@...onical.com, khalid.elmously@...onical.com, philip.cox@...onical.com, linux-kernel@...r.kernel.org, linux-kselftest@...r.kernel.org, linux-doc@...r.kernel.org Subject: Re: [PATCH v13 1/3] x86/tdx: Add TDX Guest attestation interface driver On 9/14/22 9:12 AM, Dave Hansen wrote: > On 9/14/22 08:36, Sathyanarayanan Kuppuswamy wrote: >> When we initially submitted the attestation patches, virt/coco folder >> was not created. I initially kept this driver in platform/x86/, but >> later moved to arch/x86/coco based on the review comments in v4. There >> was a discussion about the need for a new config and the location of >> the driver. The outcome of that discussion is, since this is not a >> traditional driver, but a basic TDX feature, we don't need a special >> config and the code can be maintained in the arch/x86/coco folder. > > Could you please include the following in this set somewhere: > > "The code to do the SEV analog of this TDX functionality is in > ___insert_path_here____. This code is different from that because > ______reason______ so it is instead placed in ____other_path____." > > ? Ok. I will include it in the cover letter. -- Sathyanarayanan Kuppuswamy Linux Kernel Developer
Powered by blists - more mailing lists