From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Maciej S. Szmigiero" Date: Thu, 11 Nov 2021 23:53:27 +0000 Subject: Re: [PATCH v5.5 00/30] KVM: Scalable memslots implementation Message-Id: List-Id: References: <20211104002531.1176691-1-seanjc@google.com> In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Sean Christopherson Cc: James Morse , Alexandru Elisei , Suzuki K Poulose , Atish Patra , David Hildenbrand , Cornelia Huck , Claudio Imbrenda , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , linux-arm-kernel@lists.infradead.org, kvmarm@lists.cs.columbia.edu, linux-mips@vger.kernel.org, kvm@vger.kernel.org, kvm-ppc@vger.kernel.org, kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, Ben Gardon , Marc Zyngier , Huacai Chen , Aleksandar Markovic , Paul Mackerras , Anup Patel , Paul Walmsley , Palmer Dabbelt , Albert Ou , Christian Borntraeger , Janosch Frank , Paolo Bonzini On 09.11.2021 02:21, Sean Christopherson wrote: > On Tue, Nov 09, 2021, Maciej S. Szmigiero wrote: >> On 04.11.2021 01:25, Sean Christopherson wrote: >> By the way, do you want your patches and my non-invasive patches (patches >> below number 23) merged without waiting for the rest of the series to be >> fully ready? >> >> This way there is less risk of conflicting changes to KVM being merged >> in meantime while we are still discussing the remaining patches. >> Or worse - changes that don't conflict but subtly break some assumptions >> that the code relies on. >> >> For this reason I am strongly for merging them independently from the >> more invasive parts. > > Merging them as soon as they're ready would also be my preference. That said, > I'm hoping we can get the entire implemenation queued up for 5.17 sooner than > later. I'll do my best to respond quickly to try and make that happen. > Finished going through all the patches, with small nits they do make sense to me - thanks Sean. I will prepare an updated (and tested!) next version of this patch set, however this may take about two+ weeks as I have other, more urgent work to do right now. Thanks, Maciej