[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e6296f511bb4fae4696ec19d5777103044f3aad9.camel@intel.com>
Date: Mon, 9 Jan 2023 10:30:31 +0000
From: "Huang, Kai" <kai.huang@...el.com>
To: "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"Hansen, Dave" <dave.hansen@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
CC: "Luck, Tony" <tony.luck@...el.com>,
"bagasdotme@...il.com" <bagasdotme@...il.com>,
"ak@...ux.intel.com" <ak@...ux.intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
"kirill.shutemov@...ux.intel.com" <kirill.shutemov@...ux.intel.com>,
"Christopherson,, Sean" <seanjc@...gle.com>,
"Chatre, Reinette" <reinette.chatre@...el.com>,
"pbonzini@...hat.com" <pbonzini@...hat.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"Yamahata, Isaku" <isaku.yamahata@...el.com>,
"peterz@...radead.org" <peterz@...radead.org>,
"Shahar, Sagi" <sagis@...gle.com>,
"imammedo@...hat.com" <imammedo@...hat.com>,
"Gao, Chao" <chao.gao@...el.com>,
"Brown, Len" <len.brown@...el.com>,
"sathyanarayanan.kuppuswamy@...ux.intel.com"
<sathyanarayanan.kuppuswamy@...ux.intel.com>,
"Huang, Ying" <ying.huang@...el.com>,
"Williams, Dan J" <dan.j.williams@...el.com>
Subject: Re: [PATCH v8 05/16] x86/virt/tdx: Implement functions to make
SEAMCALL
On Fri, 2023-01-06 at 09:29 -0800, Dave Hansen wrote:
> The subject here is a bit too specific. This patch isn't just
> "implementing functions". There are more than just functions here. The
> best subject is probably:
>
> Add SEAMCALL infrastructure
Yes this is better. Thanks.
>
> But that's rather generic by necessity because this patch does several
> _different_ logical things:
>
> * Wrap TDX_MODULE_CALL so it can be used for SEAMCALLs with host=1
> * Add handling to TDX_MODULE_CALL to allow it to handle specifically
> host-side error conditions
> * Add high-level seamcall() function with actual error handling
>
> It's probably also worth noting that the code that allows "host=1" to be
> passed to TDX_MODULE_CALL is dead code in mainline right now. It
> probably shouldn't have been merged this way, but oh well.
>
> I don't know that you really _need_ to split this up, but I'm just
> pointing out that mashing three different logical things together makes
> it hard to write a coherent Subject. But, I've seen worse.
Agreed.
To me seems "Add SEAMCALL infrastructure" is good enough, but I can split up if
you want me to.
Powered by blists - more mailing lists