[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CABgObfZWjGc0FT2My_oEd6V8ZxYHD-RejndbU_FipuADgJkFbw@mail.gmail.com>
Date: Wed, 30 Oct 2024 15:48:08 +0100
From: Paolo Bonzini <pbonzini@...hat.com>
To: "Huang, Kai" <kai.huang@...el.com>
Cc: 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, 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 Tue, Oct 29, 2024 at 1:24 AM Huang, Kai <kai.huang@...el.com> wrote:
> >> 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?
>
> 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?
Yes, I have now pushed a new kvm-coco-queue.
> Adding the patch which adds the script to this series is another topic.
> I can certainly do if Dave is fine.
It's better since future patches will almost certainly regenerate the file.
Can you post a followup patch to this thread,, like "9/8", that adds
the script? Then maintainers can decide whether to pick it.
Thanks,
Paolo
Powered by blists - more mailing lists