mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Huang, Kai" <kai.huang@intel.com>
To: Tom Lendacky <thomas.lendacky@amd.com>,
	<linux-kernel@vger.kernel.org>,
	"Kalra, Ashish" <Ashish.Kalra@amd.com>
Cc: <x86@kernel.org>, <dave.hansen@intel.com>,
	<kirill.shutemov@linux.intel.com>, <tglx@linutronix.de>,
	<bp@alien8.de>, <mingo@redhat.com>, <hpa@zytor.com>,
	<luto@kernel.org>, <peterz@infradead.org>, <chao.gao@intel.com>,
	<bhe@redhat.com>, <nik.borisov@suse.com>, <pbonzini@redhat.com>
Subject: Re: [PATCH 0/4] TDX host: kexec() support
Date: Mon, 5 Feb 2024 14:50:58 +0800	[thread overview]
Message-ID: <23b05fe0-60c5-4cd4-bfe8-b706c34d23ac@intel.com> (raw)
In-Reply-To: <c86203a5-0223-4824-888e-76ff9565e178@amd.com>



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!

  reply	other threads:[~2024-02-05  6:51 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-31 11:31 Huang, Kai
2024-01-31 11:31 ` [PATCH 1/4] x86/coco: Add a new CC attribute to unify cache flush during kexec Huang, Kai
2024-02-19 16:16   ` Borislav Petkov
2024-02-19 19:45     ` Tom Lendacky
2024-02-19 20:32       ` Borislav Petkov
2024-02-19 22:09         ` Tom Lendacky
2024-02-20  2:57           ` Huang, Kai
2024-02-20 14:40             ` Tom Lendacky
2024-02-20 14:28           ` Borislav Petkov
2024-02-20 14:47             ` Tom Lendacky
2024-02-20 20:07               ` Huang, Kai
2024-02-20 22:30                 ` Tom Lendacky
2024-02-21  1:38                   ` Huang, Kai
2024-02-21  9:28                   ` Borislav Petkov
2024-02-22 11:49                     ` Huang, Kai
2024-02-23  3:13                       ` Dave Young
2024-02-23 10:41                     ` Dave Young
2024-02-28  2:54                       ` Dave Young
2024-02-28  9:21                         ` Huang, Kai
2024-02-28 11:02                           ` Borislav Petkov
2024-02-28 22:21                             ` Huang, Kai
2024-02-28 10:44                         ` Borislav Petkov
2024-02-20  3:12     ` Huang, Kai
2024-01-31 11:31 ` [PATCH 2/4] x86/virt/tdx: Advertise the CC_ATTR_HOST_MEM_INCOHERENT for TDX host Huang, Kai
2024-01-31 17:11   ` Dave Hansen
2024-02-01 14:42     ` Huang, Kai
2024-01-31 11:31 ` [PATCH 3/4] x86/kexec(): Reset TDX private memory on platforms with TDX erratum Huang, Kai
2024-01-31 21:21   ` Dave Hansen
2024-01-31 22:03     ` Kirill A. Shutemov
2024-02-01 14:22       ` Huang, Kai
2024-02-01 14:39         ` Kirill A. Shutemov
2024-02-01 14:47           ` Huang, Kai
2024-02-01 16:57           ` Dave Hansen
2024-02-05  6:49             ` Huang, Kai
2024-02-01 14:35     ` Huang, Kai
2024-02-02  0:54   ` Edgecombe, Rick P
2024-02-05  6:44     ` Huang, Kai
2024-01-31 11:31 ` [PATCH 4/4] x86/virt/tdx: Remove the !KEXEC_CORE dependency Huang, Kai
2024-02-01 18:28 ` [PATCH 0/4] TDX host: kexec() support Tom Lendacky
2024-02-05  6:50   ` Huang, Kai [this message]
2024-02-06 18:56     ` Kalra, Ashish
2024-02-07  1:43       ` Huang, Kai

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=23b05fe0-60c5-4cd4-bfe8-b706c34d23ac@intel.com \
    --to=kai.huang@intel.com \
    --cc=Ashish.Kalra@amd.com \
    --cc=bhe@redhat.com \
    --cc=bp@alien8.de \
    --cc=chao.gao@intel.com \
    --cc=dave.hansen@intel.com \
    --cc=hpa@zytor.com \
    --cc=kirill.shutemov@linux.intel.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=luto@kernel.org \
    --cc=mingo@redhat.com \
    --cc=nik.borisov@suse.com \
    --cc=pbonzini@redhat.com \
    --cc=peterz@infradead.org \
    --cc=tglx@linutronix.de \
    --cc=thomas.lendacky@amd.com \
    --cc=x86@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

Powered by JetHome