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 82CDEC001DE for ; Tue, 15 Aug 2023 17:16:55 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S238485AbjHORQ0 (ORCPT ); Tue, 15 Aug 2023 13:16:26 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:34858 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S234364AbjHORP4 (ORCPT ); Tue, 15 Aug 2023 13:15:56 -0400 Received: from mail-yb1-xb4a.google.com (mail-yb1-xb4a.google.com [IPv6:2607:f8b0:4864:20::b4a]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 385EC19B5 for ; Tue, 15 Aug 2023 10:15:55 -0700 (PDT) Received: by mail-yb1-xb4a.google.com with SMTP id 3f1490d57ef6-d68c0f22fc9so6173636276.0 for ; Tue, 15 Aug 2023 10:15:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1692119754; x=1692724554; h=content-transfer-encoding:cc:to:from:subject:message-id:references :mime-version:in-reply-to:date:from:to:cc:subject:date:message-id :reply-to; bh=h4pRofXYscuxJwlZlec+kz5JByk1VStjcQk6pNX8VCg=; b=0ULGW8lrz4LAfQvUr6zW2RUHxg7wnB8mbW6D5bd2rDtC7t6jWPtR/lVCZvnMtK039v Gg8JyKieoo8YzZWKJSwsneurYfUwDhsBEjHR8BDDFIcMNXvxQFl1SY6+8po7yWKtX3gK 0M47n08PCbwSAAAHpnB5NZUa5PJ3jqM0sFJYHYCV1+uFsvROyNCULug2lOezvw4KSxiC SwvzuqKN0keYa4/1ydFK2xGN83du5F8hP7y28i8MbkevBr7RMbIjQF8iEl3lxI4AS4rj O6jyhFmalRm5sDGo51MDmx9Yc7ibOQgbEesKJpyN5wkexREqBNWTi2YgoIds/heBTaQl JrNg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692119754; x=1692724554; h=content-transfer-encoding:cc:to:from:subject:message-id:references :mime-version:in-reply-to:date:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=h4pRofXYscuxJwlZlec+kz5JByk1VStjcQk6pNX8VCg=; b=Hx0e5Tc2eONPAjW2MAx7HdTVUO7Ua0uC/hgTwjJDow7rxR4RGPonP2R3hXBE3FYwlz ttc0XkoBH3fv27MxKsCli2GPwVi+Me31HVS0+8RogzxVfcnejK/6EL7H6mOm4A+PHPzd U0y7xWFZKsFT088X3LkbXsUZsHUzTHDhBK6jPuwQ1vBM2FLl60KlkZcVVluWXpsFSDuY vq+VERbgXZw6P4szSdFLY7Q1+D1p1pIRLk8a/GWxbCTmGjKyNKUKTa+bpsSFqNUKILxJ KsIwADekdyCl+w5rlxXMOCjrT2yCLH9bxraI2zTXkdXILPHVkoJcebJCT3ceyW1H6Kk5 oE9w== X-Gm-Message-State: AOJu0YyfLW5mpLS8SZkwGDlqwSsBYwyS99ae3+8O4jJ7+ovXrhfp2DaT Poe7ZaQXidOy4pHnMibYgw1kmHMByFE= X-Google-Smtp-Source: AGHT+IEdTpAtlbhdDz4CSAmHfwiSyntmeRr/8GY1hRZWQcWfFLbFbn/FO7WCsNQ5MIITNcxj8ryCZ17c50c= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a25:890e:0:b0:d08:95:76d with SMTP id e14-20020a25890e000000b00d080095076dmr40567ybl.6.1692119754466; Tue, 15 Aug 2023 10:15:54 -0700 (PDT) Date: Tue, 15 Aug 2023 17:15:53 +0000 In-Reply-To: Mime-Version: 1.0 References: <20230811045127.3308641-1-rananta@google.com> Message-ID: Subject: Re: [PATCH v9 00/14] KVM: arm64: Add support for FEAT_TLBIRANGE From: Sean Christopherson To: Raghavendra Rao Ananta Cc: Oliver Upton , Marc Zyngier , James Morse , Suzuki K Poulose , Paolo Bonzini , Huacai Chen , Zenghui Yu , Anup Patel , Atish Patra , Jing Zhang , Reiji Watanabe , Colton Lewis , David Matlack , Fuad Tabba , linux-arm-kernel@lists.infradead.org, kvmarm@lists.linux.dev, linux-mips@vger.kernel.org, kvm-riscv@lists.infradead.org, linux-riscv@lists.infradead.org, linux-kernel@vger.kernel.org, kvm@vger.kernel.org Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Tue, Aug 15, 2023, Raghavendra Rao Ananta wrote: > On Mon, Aug 14, 2023 at 5:52=E2=80=AFPM Sean Christopherson wrote: > > > > On Mon, Aug 14, 2023, Raghavendra Rao Ananta wrote: > > > On Mon, Aug 14, 2023 at 4:16=E2=80=AFPM Sean Christopherson wrote: > > > > > > > > On Fri, Aug 11, 2023, Raghavendra Rao Ananta wrote: > > > > > The series is based off of upstream v6.5-rc1. > > > > > > > > Lies! :-) > > > > > > > > This is based off one of the kvmarm.git topic branches (I didn't bo= ther to figure > > > > out which one), not v6.5-rc1. > > > > > > > Sorry, what am I missing here? My git log is as follows: > > > > Hmm, not sure what's going on. Maybe I misinterpreted why `git am` was= failing? > > I assumed it was because there were objects in kvmarm that I didn't hav= e locally, > > and fetching kvmarm allowed am to complete, though with 3-way merges, w= hich IIUC > > shouldn't have been necessary if I was using the exact same base. Or m= aybe I > > messed up and didn't actually reset to 6.5-rc1. > > > > > $ git log --oneline upstream_tlbi_range_v9 > > > 5025857507abe (upstream_tlbi_range_v9) KVM: arm64: Use TLBI > > > range-based instructions for unmap > > > 5c0291b99a8fc KVM: arm64: Invalidate the table entries upon a range > > > 8c46b54d4aaec KVM: arm64: Flush only the memslot after write-protect > > > 231abaeb7ffc2 KVM: arm64: Implement kvm_arch_flush_remote_tlbs_range(= ) > > > 5ec291b863309 KVM: arm64: Define kvm_tlb_flush_vmid_range() > > > 5bcd7a085c34e KVM: arm64: Implement __kvm_tlb_flush_vmid_range() > > > ea08f9dff7e5b arm64: tlb: Implement __flush_s2_tlb_range_op() > > > b3178687947c9 arm64: tlb: Refactor the core flush algorithm of __flus= h_tlb_range > > > a4850fa988eef KVM: Move kvm_arch_flush_remote_tlbs_memslot() to commo= n code > > > 306dc4e6afd37 KVM: Allow range-based TLB invalidation from common cod= e > > > d02785a0a1e01 KVM: Remove CONFIG_HAVE_KVM_ARCH_TLB_FLUSH_ALL > > > 136fa2d254537 KVM: arm64: Use kvm_arch_flush_remote_tlbs() > > > e35c68a75170d KVM: Declare kvm_arch_flush_remote_tlbs() globally > > > 5d592777b9bba KVM: Rename kvm_arch_flush_remote_tlb() to > > > kvm_arch_flush_remote_tlbs() > > > 06c2afb862f9d (tag: v6.5-rc1, tag: linux/v6.5-rc1) Linux 6.5-rc1 > > > c192ac7357683 MAINTAINERS 2: Electric Boogaloo > > > f71f64210d698 Merge tag 'dma-mapping-6.5-2023-07-09' of > > > git://git.infradead.org/users/hch/dma-mapping > > > ... > > > > > > Isn't the commit, 06c2afb862f9d (06c2afb862f9d (tag: v6.5-rc1, tag: > > > linux/v6.5-rc1) Linux 6.5-rc1) the 'base' commit? > > > > Ya, should be. > > > > Either way, even if this is PEBKAC on my end, using --base would be nic= e, e.g. > > then you can definitely say it's my fault ;-) > > > I'll consider this, and thanks for the confirmation. Confirmed PEBKAC, I reset to v6.5-rc2, not rc1. My apologies, and thanks f= or being gentle.