[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <08c6bb42-c068-4dc1-8b97-0c53fb896a58@intel.com>
Date: Tue, 29 Oct 2024 10:39:54 +1300
From: "Huang, Kai" <kai.huang@...el.com>
To: Paolo Bonzini <pbonzini@...hat.com>, <dave.hansen@...el.com>,
<kirill.shutemov@...ux.intel.com>, <tglx@...utronix.de>, <bp@...en8.de>,
<peterz@...radead.org>, <mingo@...hat.com>, <hpa@...or.com>,
<dan.j.williams@...el.com>, <seanjc@...gle.com>
CC: <x86@...nel.org>, <linux-kernel@...r.kernel.org>, <kvm@...r.kernel.org>,
<rick.p.edgecombe@...el.com>, <isaku.yamahata@...el.com>,
<adrian.hunter@...el.com>, <nik.borisov@...e.com>, Klaus Kiwi
<kkiwi@...hat.com>
Subject: Re: [PATCH v6 00/10] TDX host: metadata reading tweaks, bug fix and
info dump
On 29/10/2024 7:35 am, Paolo Bonzini wrote:
> On 10/28/24 13:41, Kai Huang wrote:
>> This series does necessary tweaks to TDX host "global metadata" reading
>> code to fix some immediate issues in the TDX module initialization code,
>> with intention to also provide a flexible code base to support sharing
>> global metadata to KVM (and other kernel components) for future needs.
>
> Kai/Dave/Rick,
>
> the v6 of this series messes up the TDX patches for KVM, which do not
> apply anymore. I can work on a rebase myself for the sake of putting
> this series in kvm-coco-queue; but please help me a little bit by
> including in the generated data all the fields that KVM needs.
I have already rebased the impacted patches and pushed to here:
https://github.com/intel/tdx/commits/kvm-tdxinit-host-metadata-v6/
.. which includes:
1) this series
2) TDX module init in KVM patches
3) 3 additional patches to reading more metadata and share to KVM.
Besides the above, one minor update is needed to the KVM TDX patch
KVM: TDX: Get system-wide info about TDX module on initialization
.. because now the cpuid_config_value is now a 2-dimensional array:
The updated patch can be found here:
https://github.com/intel/tdx/commit/fd7947118b76f6d4256bc4228e03e73262e67ba2
>
> Are you able to send quickly a v7 that includes these fields, and that
> also checks in the script that generates the files?
Yeah I can do. But for KVM to use those fields, we will also need
export those metadata. Do you want me to just include all the 3 patches
that are mentioned in the above item 3) to v7?
Hi Dave,
Could you also comment whether this is OK to you?
>
> Emphasis on "quickly". No internal review processes of any kind, please.
Yeah understood.
Powered by blists - more mailing lists