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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id A6DADC27C76 for ; Wed, 25 Jan 2023 17:22:06 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S236029AbjAYRWE (ORCPT ); Wed, 25 Jan 2023 12:22:04 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:46612 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235476AbjAYRWC (ORCPT ); Wed, 25 Jan 2023 12:22:02 -0500 Received: from mail-yb1-xb29.google.com (mail-yb1-xb29.google.com [IPv6:2607:f8b0:4864:20::b29]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id ECD3410A97 for ; Wed, 25 Jan 2023 09:22:01 -0800 (PST) Received: by mail-yb1-xb29.google.com with SMTP id x4so22153415ybp.1 for ; Wed, 25 Jan 2023 09:22:01 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=+NF7WOwKXStbVcCBmnQTR8aAYHjwReQdf6MvWz/ieQE=; b=G/sP0Ge2BbmLK5C1fYqIhHmfO9YiRHy87eRqbWpmlZctgb1Mjd3hQa4bOwD180MWX6 N9m5BZ5ghS2tzwTNr12nV3VeSN0+z9yP0c4kJa8fVHf0liLZpx9LSNTEL28uc4R/m8Xd DTt9dY/swPExNObKMFXnORILtXrqvfvPIy7kzOUkT25jJo53AbsZlXcJaaoY0pxtCLXS qgm7XaZfzBEKVqNPbBdF0AhzVYtmjGNYtzFnqQUr3odJs29myMNgBOQe8LMz9PeTVJLp 7+pVgI1I+vSb3zqVmxeKhnMsVmNFvn/PsYcbOlBZDilIwwcmDqrHgsUVs8ak5XGd8/tq 3RgQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=+NF7WOwKXStbVcCBmnQTR8aAYHjwReQdf6MvWz/ieQE=; b=W/8qFUt2y4fZfZn3UOZRyVwjl13w+o2cQtaSvSlTWF1O25Eq1kKeFX40fPYmD5H/4E lmvkU/9h5lXx5NKeJa2b+/HduVNQ5rOG1EiK/V8F2t9yzO0OCBHyFzXibM/7xmUQ7NII PQUFzgXJ9rqy8yijIcsCtDfi7ek60HZ3uN91J43cR9eoFPTEkaczLUqEXwyssq4ehYo+ Bb/sIGe2ySfQ67LpzXAJWpYxoornE4ooo5soFRDSF2hSY26Rsoyd89Ko7vtN7a9TESg0 9ahej3I7vjURc5stXjgWKOsCcjJZhT1yorZ0rMBtcz5klD/w4ELhH5tcYeNBLixu6MKK 9obg== X-Gm-Message-State: AFqh2kqztD+aEhuCXu7D9Xga6Tlya6gGHqHtnzRCar7SQuo/PqeN9FYT tvC4wIl4e6Rc349QF6ND2qrMAC6SXghoeJvmhsRWyA== X-Google-Smtp-Source: AMrXdXu3jKBxFWKV9U7HEoc8nZkdzpu/vB3yVyIUHmWHNLUO+5YjJYHaG1m9/rmSDsx5131N51uq+J+p+rywDrfAr5Q= X-Received: by 2002:a25:1984:0:b0:7fe:e7f5:e228 with SMTP id 126-20020a251984000000b007fee7f5e228mr1798951ybz.582.1674667320995; Wed, 25 Jan 2023 09:22:00 -0800 (PST) MIME-Version: 1.0 References: <20230119173559.2517103-1-dmatlack@google.com> In-Reply-To: From: David Matlack Date: Wed, 25 Jan 2023 09:21:34 -0800 Message-ID: Subject: Re: [PATCH 0/7] KVM: Add a common API for range-based TLB invalidation To: Oliver Upton Cc: Sean Christopherson , Paolo Bonzini , Marc Zyngier , James Morse , Suzuki K Poulose , Zenghui Yu , Huacai Chen , Aleksandar Markovic , Anup Patel , Atish Patra , Paul Walmsley , Palmer Dabbelt , Albert Ou , linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev, kvmarm@lists.cs.columbia.edu, linux-mips@vger.kernel.org, kvm@vger.kernel.org, kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org, Raghavendra Rao Ananta Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-mips@vger.kernel.org On Tue, Jan 24, 2023 at 4:51 PM Oliver Upton wrote: > On Wed, Jan 25, 2023 at 12:46:59AM +0000, Sean Christopherson wrote: > > On Thu, Jan 19, 2023, David Matlack wrote: > > > > Did a quick read through, didn't see anything I disagree with. > > LGTM for the tiny amount of arm64 changes, though I imagine David will > do a v2 to completely get rid of the affected Kconfig. Thanks both for taking a look. > > Is there any urgency to getting this merged? If not, due to the dependencies > > with x86 stuff queued for 6.3, and because of the cross-architecture changes, it > > might be easiest to plan on landing this in 6.4. That would allow Paolo to create > > an immutable topic branch fairly early on. > > +1, that buys us some time to go through the rounds on the arm64 side > such that we could possibly stack the TLBIRANGE work on top. The main benefit of merging in 6.3 would be to make Raghavendra's life simpler/easier so he can build the next version of his arm64 TLBI series on top. But I guess he can still do that with a topic branch. I'll go ahead and send a v2 on top of the changes from Hou you queued for 6.3, Sean, and we can plan on landing that in 6.4 (barring any further feedback or conflicts).