From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D360FC433EF for ; Tue, 9 Nov 2021 01:39:01 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id BC375610F8 for ; Tue, 9 Nov 2021 01:39:01 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S239308AbhKIBlp (ORCPT ); Mon, 8 Nov 2021 20:41:45 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:50606 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236272AbhKIBll (ORCPT ); Mon, 8 Nov 2021 20:41:41 -0500 Received: from mail-pf1-x432.google.com (mail-pf1-x432.google.com [IPv6:2607:f8b0:4864:20::432]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 1C9A3C03649F for ; Mon, 8 Nov 2021 17:21:13 -0800 (PST) Received: by mail-pf1-x432.google.com with SMTP id z6so2061552pfe.7 for ; Mon, 08 Nov 2021 17:21:13 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=xrX5PIQ5N2CnAG0B54w4TYQMlOw3gRJk552Ipp+ebKw=; b=Stz43RdVom5q6hSvN+LnhdAH1B5D0RUDmznyrJp0pQFRjJeWUrzR/udLPaY2tilNCt XcgrdLFIIf2+mR8m54M6dT+Dbrc35be5RRM9b9uL9pOdJ4j7hQwoxKcdUZiCi2W8rFeo mmXBUYtpY4TQWJozh8/OxpMOOMnVYCLM8GwnYcFgDNGHVKOZqBpYEqqfKv0BxApaEO6w QHgCpUm2hA6iGp0NqZEk59gkrY4Hh/+mLGmE93ORS8+YVRoDiSXYWhEz8HkG7mLHejSo f65DHHDi9o/I209K1+WG4QDyN4k9mmBRl/VShVuSsU+pG0yGr+qfqYoTiN2J1n0hf0oV 3pUw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=xrX5PIQ5N2CnAG0B54w4TYQMlOw3gRJk552Ipp+ebKw=; b=CfQt2KBEBQY88VUZGK6C+dz2ea1iN0XeqkQWoH0glWfKY+mEpnA9Xy2K7J9Xb+s0cr Kbon6eaJf0bnpdtyBxkxzTwiyV8+24ZDR8M6U/qJMkhGtfvdfTyky+LbJjzywFvnG4PW sOGWWihQgjLcuJ2IgHZm+qJPFxIWNxpTrDGvoqJLeg6BAbylOixH4lajf32zaNbTldUo e8TNGJmbmTJJB2S4aqSwYYG3XUdZBE/iuuZbgfzZLNzO5CxnL50gE3sfEBnht3/16YwU ClPKfTdn1MiiEhxXbIfE6wtmiywLI4kVCIG8W6WxnYaKHI23k7o3cuc0WCVHlL4oDbf2 cpxA== X-Gm-Message-State: AOAM533/LgGkNQ/OWooefP6f3/ZRvqUxJ7XiPX20CU644sR5AP0h8FVI aWBBF1N4auBxJudiiBwhDRmqmg== X-Google-Smtp-Source: ABdhPJzT4cwDWE/OiPQTr+XYp5T2lNnL8iaG9fSc3ur50OFq8TyJ/z2y4+XiWK6EYq8MqHpQV5QIIA== X-Received: by 2002:a63:8a4a:: with SMTP id y71mr2992478pgd.378.1636420872463; Mon, 08 Nov 2021 17:21:12 -0800 (PST) Received: from google.com (157.214.185.35.bc.googleusercontent.com. [35.185.214.157]) by smtp.gmail.com with ESMTPSA id t13sm11751282pfl.214.2021.11.08.17.21.11 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Mon, 08 Nov 2021 17:21:11 -0800 (PST) Date: Tue, 9 Nov 2021 01:21:07 +0000 From: Sean Christopherson To: "Maciej S. Szmigiero" 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 Subject: Re: [PATCH v5.5 00/30] KVM: Scalable memslots implementation Message-ID: References: <20211104002531.1176691-1-seanjc@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org 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.