[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YioQVLY9Q5OWoqF4@zn.tnic>
Date: Thu, 10 Mar 2022 15:51:00 +0100
From: Borislav Petkov <bp@...en8.de>
To: "Kirill A. Shutemov" <kirill.shutemov@...ux.intel.com>
Cc: tglx@...utronix.de, mingo@...hat.com, dave.hansen@...el.com,
luto@...nel.org, peterz@...radead.org,
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
Subject: Re: [PATCHv5 02/30] x86/tdx: Provide common base for SEAMCALL and
TDCALL C wrappers
On Thu, Mar 10, 2022 at 05:44:04PM +0300, Kirill A. Shutemov wrote:
> I'm fine moving where you want. But I want to make sure we are on the same
> page: this code is common for guest and host TDX. I think VMX referes more
> to host side of the thing, no?
Well, that patch has host-side stuff too.
If we have to be pedantic, this should be in
arch/x86/virt/shared/vmx/tdx
or so but that's bikeshedding gone out of control to me.
And it isn't generic, as pointed out earlier, so arch/x86/virt/ does not
fit either.
So I'd think of something with "tdx" in the pathname and
arch/x86/virt/vmx/tdx/ is kinda the only one we agreed upon as a path...
Thx.
--
Regards/Gruss,
Boris.
https://people.kernel.org/tglx/notes-about-netiquette
Powered by blists - more mailing lists