[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1fdb2533412513078a92398d5ae0a0159d08647e.camel@intel.com>
Date: Fri, 7 Jun 2024 22:54:51 +0000
From: "Edgecombe, Rick P" <rick.p.edgecombe@...el.com>
To: "pbonzini@...hat.com" <pbonzini@...hat.com>
CC: "seanjc@...gle.com" <seanjc@...gle.com>, "Huang, Kai"
<kai.huang@...el.com>, "sagis@...gle.com" <sagis@...gle.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, "Aktas, Erdem"
<erdemaktas@...gle.com>, "Zhao, Yan Y" <yan.y.zhao@...el.com>,
"dmatlack@...gle.com" <dmatlack@...gle.com>, "kvm@...r.kernel.org"
<kvm@...r.kernel.org>, "isaku.yamahata@...il.com" <isaku.yamahata@...il.com>
Subject: Re: [PATCH v2 00/15] TDX MMU prep series part 1
On Fri, 2024-06-07 at 13:39 +0200, Paolo Bonzini wrote:
>
> Yes, now we're talking indeed. Mostly it's cosmetic tweaks or requests
> to fix/improve a few comments, but overall it's very pleasing and
> algorithmically clear code to read. Kudos to everyone involved.
>
> I don't expect any big issues with v3.
Thanks so much for the review. We'll try to turn this around quickly.
In the meantime, we will likely be posting two generic series that were split
out of this one:
- Making max_gfn configurable per-vm.
- Create a quirk for memslot deletion zapping all PTEs.
Powered by blists - more mailing lists