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 17AE8C001E0 for ; Tue, 15 Aug 2023 00:53:45 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S233811AbjHOAxQ (ORCPT ); Mon, 14 Aug 2023 20:53:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45302 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233948AbjHOAxK (ORCPT ); Mon, 14 Aug 2023 20:53:10 -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 C78391BF2 for ; Mon, 14 Aug 2023 17:52:48 -0700 (PDT) Received: by mail-yb1-xb4a.google.com with SMTP id 3f1490d57ef6-d67a458ff66so3912571276.3 for ; Mon, 14 Aug 2023 17:52:48 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1692060752; x=1692665552; 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=hk15mUEG36mYzoWqdyXNILxXbUGFuZdN5ezEkvLZ3iM=; b=SUKnvazqj9CVjAezsoD2+y+B/lascXFbPfh2BmPWUTPhsp2ltMrajsTckozDu9ifdm uRoTdnCgOM98B7Rnb91Ve9c/MBRF5IHK3nGacQ54NRHNp4jfWACljRlSNeWuoRdL+3na CtHqlJoC59YHPayYcYzVEhCEfMbZsPVJQIkTDsx0J6ehfskI+bg3C/TTqGB4GfV7K9Vn rRDM2yi+re6usECld7Z4U2WK/2ghsl54KPV4Ycl6v1kRxR+u2a297eNSVYm3jPrYQCL2 cXFmXO9Zt4S3exCCMfQ/QP9nNjQaIR5tBPHnG0PDbMprpJdiffEDLgQQkSHFXTPIaHgD 6rOw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692060752; x=1692665552; 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=hk15mUEG36mYzoWqdyXNILxXbUGFuZdN5ezEkvLZ3iM=; b=Avh7oRrJvVr9Eb8clbkUTr3z/7yurm16F8BKdzUPKyxBSO3MMpG4ZhTSMVek/yfKIZ lUE/bdpG27Y4JAD2ZIj2Dx4QuqlY9dkt1SQog25yRFEt+isD6XifJNY3DE/GkirwrCAY gYyEXPoSs1sthg1Ph4ycSdxWUX2bMEkKsHh+6nKNFvX6e3t2UGem2SUz5T3hU223jax+ Zp2KM+3kfHx38xvV66OoQbtK5o3F0gvh049h8q3+/xkmiOFothFBbFmi/2lJPyhdSBL+ PnvEx5vR8vhIBxtsZODf03C5JJRlzy9oDqrs/C5YmN5rHFWqStkZskVsmPsbK/rkVfip cMyA== X-Gm-Message-State: AOJu0Yy+5TRf3+d0SyQFgdbItwA810ngzeeqfYxYD27eBVGr3Uptvn/b d46ONlLUwKeHEcDzX1mSlR97RS0tmUE= X-Google-Smtp-Source: AGHT+IEm/gyjzby2m0z7Th7h1NzS+zVz9W6iAdmwDKQNzO5UYu/Tw93ovcYoaLNJ0fJilJkbmSYm3tW9J7c= X-Received: from zagreus.c.googlers.com ([fda3:e722:ac3:cc00:7f:e700:c0a8:5c37]) (user=seanjc job=sendgmr) by 2002:a25:7443:0:b0:d20:7752:e384 with SMTP id p64-20020a257443000000b00d207752e384mr148317ybc.3.1692060751838; Mon, 14 Aug 2023 17:52:31 -0700 (PDT) Date: Mon, 14 Aug 2023 17:52:30 -0700 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 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 bother= 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 fai= ling? I assumed it was because there were objects in kvmarm that I didn't have lo= cally, and fetching kvmarm allowed am to complete, though with 3-way merges, which= IIUC shouldn't have been necessary if I was using the exact same base. Or maybe= 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 __flush_tl= b_range > a4850fa988eef KVM: Move kvm_arch_flush_remote_tlbs_memslot() to common co= de > 306dc4e6afd37 KVM: Allow range-based TLB invalidation from common code > 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 > ... >=20 > 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 nice, e= .g. then you can definitely say it's my fault ;-) > > Please try to incorporate git format-patch's "--base" option into your = workflow, > > e.g. I do "git format-patch --base=3DHEAD~$nr" where $nr is the number = of patches > > I am posting. > > > > It's not foolproof, e.g. my approach doesn't help if I have a local pat= ch that > > I'm not posting, but 99% of the time it Just Works and eliminates any a= mbuitity. > > > > You can also do "--base=3Dauto", but that only does the right thing if = your series > > has its upstream branch set to the base/tree that you want your patches= applied > > to (I use the upstream branch for a completely different purpose for my= dev branches).