[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <23b05fe0-60c5-4cd4-bfe8-b706c34d23ac@intel.com>
Date: Mon, 5 Feb 2024 14:50:58 +0800
From: "Huang, Kai" <kai.huang@...el.com>
To: Tom Lendacky <thomas.lendacky@....com>, <linux-kernel@...r.kernel.org>,
"Kalra, Ashish" <Ashish.Kalra@....com>
CC: <x86@...nel.org>, <dave.hansen@...el.com>,
<kirill.shutemov@...ux.intel.com>, <tglx@...utronix.de>, <bp@...en8.de>,
<mingo@...hat.com>, <hpa@...or.com>, <luto@...nel.org>,
<peterz@...radead.org>, <chao.gao@...el.com>, <bhe@...hat.com>,
<nik.borisov@...e.com>, <pbonzini@...hat.com>
Subject: Re: [PATCH 0/4] TDX host: kexec() support
On 2/02/2024 2:28 am, Tom Lendacky wrote:
> On 1/31/24 05:31, Huang, Kai wrote:
>> Currently kexec() support and TDX host are muturally exclusive in the
>> Kconfig. This series adds the TDX host kexec support so that they can
>> work together and can be enabled at the same time in the Kconfig.
>>
>> This follows Dave's suggestion to add the CC_ATTR_HOST_MEM_INCOHERENT
>> attribute to unify both Intel and AMD, instead of having Intel/AMD
>> specific checks around [1].
>>
>> Hi Tom,
>>
>> I've tested on my TDX testig machine but I don't have AMD machine to
>> test. I highly appreciate if you or any AMD guy can help to review
>> and/or test this series to make sure I didn't break anything.
>
> Hi Kai,
>
> I'm adding Ashish to the thread to take a look at this as he's been
> focusing on kexec related things recently.
>
Thanks Tom.
Hi Ashish,
I appreciate if you can help to review and test the first patch. Thanks!
Powered by blists - more mailing lists