From: "Huang, Kai" <kai.huang@intel.com>
To: Paolo Bonzini <pbonzini@redhat.com>, <dave.hansen@intel.com>,
<kirill.shutemov@linux.intel.com>, <tglx@linutronix.de>,
<bp@alien8.de>, <peterz@infradead.org>, <mingo@redhat.com>,
<hpa@zytor.com>, <dan.j.williams@intel.com>, <seanjc@google.com>
Cc: <x86@kernel.org>, <linux-kernel@vger.kernel.org>,
<kvm@vger.kernel.org>, <rick.p.edgecombe@intel.com>,
<isaku.yamahata@intel.com>, <adrian.hunter@intel.com>,
<nik.borisov@suse.com>, Klaus Kiwi <kkiwi@redhat.com>
Subject: Re: [PATCH v6 00/10] TDX host: metadata reading tweaks, bug fix and info dump
Date: Tue, 29 Oct 2024 13:23:55 +1300 [thread overview]
Message-ID: <6c8bff1a-876f-47b7-a80c-3f3a825ddbc0@intel.com> (raw)
In-Reply-To: <08c6bb42-c068-4dc1-8b97-0c53fb896a58@intel.com>
>>
>> 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?
Sorry I just realize I cannot just move all the 3 patches in item 3) to
this series since one of them depends on TDX module init KVM patch. So
yeah I can just move the patch which reads more fields for KVM to this
series but leave the rest to future patchset.
But for kvm-coco-queue purpose as mentioned in the previous reply I have
rebased those patches and pushed to github. So perhaps we can leave
them to the future patchset for the sake of keeping this series simple?
Adding the patch which adds the script to this series is another topic.
I can certainly do if Dave is fine.
next prev parent reply other threads:[~2024-10-29 0:24 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-28 12:41 Kai Huang
2024-10-28 12:41 ` [PATCH v6 01/10] x86/virt/tdx: Rename 'struct tdx_tdmr_sysinfo' to reflect the spec better Kai Huang
2024-10-28 12:41 ` [PATCH v6 02/10] x86/virt/tdx: Start to track all global metadata in one structure Kai Huang
2024-10-28 21:37 ` Dan Williams
2024-10-28 12:41 ` [PATCH v6 03/10] x86/virt/tdx: Use auto-generated code to read global metadata Kai Huang
2024-10-28 21:46 ` Dan Williams
2024-10-28 22:47 ` Huang, Kai
2024-10-28 12:41 ` [PATCH v6 04/10] x86/virt/tdx: Use dedicated struct members for PAMT entry sizes Kai Huang
2024-10-28 13:29 ` Nikolay Borisov
2024-10-28 21:51 ` Dan Williams
2024-10-28 12:41 ` [PATCH v6 05/10] x86/virt/tdx: Add missing header file inclusion to local tdx.h Kai Huang
2024-10-28 13:35 ` Nikolay Borisov
2024-10-28 21:55 ` Dan Williams
2024-10-28 12:41 ` [PATCH v6 06/10] x86/virt/tdx: Switch to use auto-generated global metadata reading code Kai Huang
2024-10-28 14:55 ` Nikolay Borisov
2024-10-28 22:08 ` Dan Williams
2024-10-28 12:41 ` [PATCH v6 07/10] x86/virt/tdx: Trim away tail null CMRs Kai Huang
2024-10-28 22:12 ` Dan Williams
2024-10-28 12:41 ` [PATCH v6 08/10] x86/virt/tdx: Reduce TDMR's reserved areas by using CMRs to find memory holes Kai Huang
2024-10-28 22:26 ` Dan Williams
2024-10-28 23:22 ` Huang, Kai
2024-10-28 12:41 ` [PATCH v6 09/10] x86/virt/tdx: Require the module to assert it has the NO_RBP_MOD mitigation Kai Huang
2024-10-28 12:41 ` [PATCH v6 10/10] x86/virt/tdx: Print TDX module version Kai Huang
2024-10-28 22:36 ` Dan Williams
2024-10-28 22:59 ` Huang, Kai
2024-10-28 17:59 ` [PATCH v6 00/10] TDX host: metadata reading tweaks, bug fix and info dump Paolo Bonzini
2024-10-28 21:50 ` Huang, Kai
2024-10-28 18:35 ` Paolo Bonzini
2024-10-28 21:39 ` Huang, Kai
2024-10-29 0:23 ` Huang, Kai [this message]
2024-10-30 14:48 ` Paolo Bonzini
2024-10-30 20:40 ` Huang, Kai
2024-10-31 10:44 ` [PATCH 9/8] x86/virt/tdx: Add the global metadata code generation script Kai Huang
2024-11-06 11:00 ` [PATCH v6 00/10] TDX host: metadata reading tweaks, bug fix and info dump 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=6c8bff1a-876f-47b7-a80c-3f3a825ddbc0@intel.com \
--to=kai.huang@intel.com \
--cc=adrian.hunter@intel.com \
--cc=bp@alien8.de \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@intel.com \
--cc=hpa@zytor.com \
--cc=isaku.yamahata@intel.com \
--cc=kirill.shutemov@linux.intel.com \
--cc=kkiwi@redhat.com \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@redhat.com \
--cc=nik.borisov@suse.com \
--cc=pbonzini@redhat.com \
--cc=peterz@infradead.org \
--cc=rick.p.edgecombe@intel.com \
--cc=seanjc@google.com \
--cc=tglx@linutronix.de \
--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
all inboxes | Powered by JetHome®