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 3ECCAC54E94 for ; Wed, 25 Jan 2023 00:47:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233616AbjAYArH (ORCPT ); Tue, 24 Jan 2023 19:47:07 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:51580 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231553AbjAYArF (ORCPT ); Tue, 24 Jan 2023 19:47:05 -0500 Received: from mail-pg1-x534.google.com (mail-pg1-x534.google.com [IPv6:2607:f8b0:4864:20::534]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 68132457D5 for ; Tue, 24 Jan 2023 16:47:04 -0800 (PST) Received: by mail-pg1-x534.google.com with SMTP id b6so12417099pgi.7 for ; Tue, 24 Jan 2023 16:47:04 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:from:to:cc:subject:date:message-id:reply-to; bh=ghxIETXzFs7vJZ8k07wa7GlexKAzC+rzARYUkXCHQHs=; b=LvjZfwXCe3mA6H4AGCqGyzVKFBo5GWM8FdhLXaayHykpzPCuRAjaElAT5Hk2ey/F40 Bh0dvjNSUfqTGb2iuj7q1O/PTP7W4gatjaXfhcEVTR9wjA0tLBMoJ0VwCZFubj/cVP55 Ivatyfw6YQ7PGbADo/BVU9RK987h/uMS90RV4WjpCsfklzdPKAdTHudb41fHEoV/AC4t QA+JdfzzdjDGfYBlxMFkykCYVfgF1+Lcr4tMwizCyX8BReSbwOSOFa9HKtzdOfc+/Z4x VkMk2QpFyvQFvDavS06hVgLrLbNgjoiC6/78xM6uAk2D8AhY1zohmPXNMphYinnluuYY oCeA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=in-reply-to:content-disposition:mime-version:references:message-id :subject:cc:to:from:date:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=ghxIETXzFs7vJZ8k07wa7GlexKAzC+rzARYUkXCHQHs=; b=bRrbVpMpoSZVZgh/ttl15wUcGKoT7bBtao8fJmYU9YQVmpZnzAsfogpgCTE5Vgt+rM Y+C0qr4uFzfpSWoAZe7Iro/nRQCc49RXuIgbDp45X3i/gVLK/osXjIQugS0uh4XP/uPX 4Rte8Bi0hiTgR9HqUnTphPVSNFXVvaVmusiitKIUrPxApIbUpVW34xlzwcpWAymTtbZa OWEFfwxlznsqds74kfViFPqutRR8/weRvaycmNtXWxTCNVflgxsnPRM2DS2qLrWsfeZI ZMwilWSg/x8fIbMATMMA1TnCS5xMQNxo5fRbFqwtKNjvf9mL824mPfMxS/Bpyh6OLZdL PWwA== X-Gm-Message-State: AO0yUKW+gQhOkPZKxYBKyB/Ohn0gwMepGV98xVuxZVy2B7qTHa4EmpxC pNQw1y9UFdgFjyLSBPXQFTkzIQ== X-Google-Smtp-Source: AK7set9F5NYwCkfGKD1bo/mJyqFfAsir2nkFX4eO7dXf2tZvBxGZyFTFZ2Lda5ZK6A3xZU2rNxPYBg== X-Received: by 2002:a62:7988:0:b0:58b:cb1b:978f with SMTP id u130-20020a627988000000b0058bcb1b978fmr382182pfc.1.1674607623688; Tue, 24 Jan 2023 16:47:03 -0800 (PST) Received: from google.com (7.104.168.34.bc.googleusercontent.com. [34.168.104.7]) by smtp.gmail.com with ESMTPSA id z6-20020aa791c6000000b005884d68d54fsm2242952pfa.1.2023.01.24.16.47.03 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 24 Jan 2023 16:47:03 -0800 (PST) Date: Wed, 25 Jan 2023 00:46:59 +0000 From: Sean Christopherson To: David Matlack Cc: Paolo Bonzini , Marc Zyngier , James Morse , Suzuki K Poulose , Oliver Upton , 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 Subject: Re: [PATCH 0/7] KVM: Add a common API for range-based TLB invalidation Message-ID: References: <20230119173559.2517103-1-dmatlack@google.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230119173559.2517103-1-dmatlack@google.com> Precedence: bulk List-ID: X-Mailing-List: kvm@vger.kernel.org On Thu, Jan 19, 2023, David Matlack wrote: > This series introduces a common API for performing range-based TLB > invalidation. This is then used to supplant > kvm_arch_flush_remote_tlbs_memslot() and pave the way for two other > patch series: > > 1. https://lore.kernel.org/kvm/20230109215347.3119271-1-rananta@google.com/ > > Adds ARM support for range-based TLB invalidation and needs a > mechanism to invoke it from common code. This series provides such a > mechanism via kvm_arch_flush_remote_tlbs_range(). > > 2. https://lore.kernel.org/kvm/20221208193857.4090582-1-dmatlack@google.com/ > > Refactors the TDP MMU into common code, which requires an API for > range-based TLB invaliation. > > This series is based on patches 29-33 from (2.), but I made some further > cleanups after looking at it a second time. > > Tested on x86_64 and ARM64 using KVM selftests. Did a quick read through, didn't see anything I disagree with. 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.