Re: [PATCH v6 00/10] TDX host: metadata reading tweaks, bug fix and info dump
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
- Subject: Re: [PATCH v6 00/10] TDX host: metadata reading tweaks, bug fix and info dump
- From: "Huang, Kai" <kai.huang@xxxxxxxxx>
- Date: Tue, 29 Oct 2024 13:23:55 +1300
- Cc: <x86@xxxxxxxxxx>, <linux-kernel@xxxxxxxxxxxxxxx>, <kvm@xxxxxxxxxxxxxxx>, <rick.p.edgecombe@xxxxxxxxx>, <isaku.yamahata@xxxxxxxxx>, <adrian.hunter@xxxxxxxxx>, <nik.borisov@xxxxxxxx>, Klaus Kiwi <kkiwi@xxxxxxxxxx>
- In-reply-to: <08c6bb42-c068-4dc1-8b97-0c53fb896a58@intel.com>
- References: <cover.1730118186.git.kai.huang@intel.com> <0b1f3c07-a1e9-4008-8de5-52b1fea7ad7b@redhat.com> <08c6bb42-c068-4dc1-8b97-0c53fb896a58@intel.com>
- User-agent: Mozilla Thunderbird
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.
[Index of Archives]
[KVM ARM]
[KVM ia64]
[KVM ppc]
[Virtualization Tools]
[Spice Development]
[Libvirt]
[Libvirt Users]
[Linux USB Devel]
[Linux Audio Users]
[Yosemite Questions]
[Linux Kernel]
[Linux SCSI]
[XFree86]