[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <78a1046cffc6db3345a65e98a7565cecb77fa302.camel@intel.com>
Date: Sat, 1 Jul 2023 08:16:50 +0000
From: "Huang, Kai" <kai.huang@...el.com>
To: "peterz@...radead.org" <peterz@...radead.org>,
"Hansen, Dave" <dave.hansen@...el.com>
CC: "kvm@...r.kernel.org" <kvm@...r.kernel.org>,
"Raj, Ashok" <ashok.raj@...el.com>,
"Luck, Tony" <tony.luck@...el.com>,
"david@...hat.com" <david@...hat.com>,
"bagasdotme@...il.com" <bagasdotme@...il.com>,
"ak@...ux.intel.com" <ak@...ux.intel.com>,
"Wysocki, Rafael J" <rafael.j.wysocki@...el.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"Chatre, Reinette" <reinette.chatre@...el.com>,
"Christopherson,, Sean" <seanjc@...gle.com>,
"pbonzini@...hat.com" <pbonzini@...hat.com>,
"mingo@...hat.com" <mingo@...hat.com>,
"Yamahata, Isaku" <isaku.yamahata@...el.com>,
"kirill.shutemov@...ux.intel.com" <kirill.shutemov@...ux.intel.com>,
"tglx@...utronix.de" <tglx@...utronix.de>,
"nik.borisov@...e.com" <nik.borisov@...e.com>,
"linux-mm@...ck.org" <linux-mm@...ck.org>,
"hpa@...or.com" <hpa@...or.com>, "Shahar, Sagi" <sagis@...gle.com>,
"imammedo@...hat.com" <imammedo@...hat.com>,
"bp@...en8.de" <bp@...en8.de>, "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>,
"x86@...nel.org" <x86@...nel.org>
Subject: Re: [PATCH v12 20/22] x86/virt/tdx: Allow SEAMCALL to handle #UD and
#GP
On Fri, 2023-06-30 at 08:16 -0700, Dave Hansen wrote:
> On 6/30/23 03:18, Huang, Kai wrote:
> > > Please, because 12,14 are callee-saved, which means we need to go add
> > > push/pop to preserve them 🙁
> > Yes.
> >
> > However those new SEAMCALLs are for TDX guest live migration support, which is
> > at a year(s)-later thing from upstreaming's point of view. My thinking is we
> > can defer supporting those new SEAMCALls until that phase. Yes we need to do
> > some assembly change at that time, but also looks fine to me.
> >
> > How does this sound?
>
> It would sound better if the TDX module folks would take that year to
> fix the module and make it nicer for Linux. :)
Yeah agreed. And we can push them to do when we find something needs to be
improved. :)
Powered by blists - more mailing lists