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 X-Spam-Level: X-Spam-Status: No, score=-13.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D7F13C433F5 for ; Fri, 10 Sep 2021 09:06:35 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id AE5B260FDC for ; Fri, 10 Sep 2021 09:06:35 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S231929AbhIJJHp convert rfc822-to-8bit (ORCPT ); Fri, 10 Sep 2021 05:07:45 -0400 Received: from frasgout.his.huawei.com ([185.176.79.56]:3758 "EHLO frasgout.his.huawei.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S231771AbhIJJHp (ORCPT ); Fri, 10 Sep 2021 05:07:45 -0400 Received: from fraeml702-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4H5VLX22N2z67hcS; Fri, 10 Sep 2021 17:04:36 +0800 (CST) Received: from lhreml715-chm.china.huawei.com (10.201.108.66) by fraeml702-chm.china.huawei.com (10.206.15.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.8; Fri, 10 Sep 2021 11:06:32 +0200 Received: from lhreml710-chm.china.huawei.com (10.201.108.61) by lhreml715-chm.china.huawei.com (10.201.108.66) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.8; Fri, 10 Sep 2021 10:06:32 +0100 Received: from lhreml710-chm.china.huawei.com ([169.254.81.184]) by lhreml710-chm.china.huawei.com ([169.254.81.184]) with mapi id 15.01.2308.008; Fri, 10 Sep 2021 10:06:31 +0100 From: Shameerali Kolothum Thodi To: Will Deacon , "linux-arm-kernel@lists.infradead.org" , Catalin Marinas CC: "kernel-team@android.com" , Marc Zyngier , Jade Alglave , "kvmarm@lists.cs.columbia.edu" , "linux-arch@vger.kernel.org" , Jonathan Cameron Subject: RE: [PATCH 0/4] Fix racing TLBI with ASID/VMID reallocation Thread-Topic: [PATCH 0/4] Fix racing TLBI with ASID/VMID reallocation Thread-Index: AQHXiraYscBrfnIwF0OIF7R8segGVaudIb7g Date: Fri, 10 Sep 2021 09:06:31 +0000 Message-ID: <753ff5ea79d54db0af83d195adcfa2b1@huawei.com> References: <20210806113109.2475-1-will@kernel.org> In-Reply-To: <20210806113109.2475-1-will@kernel.org> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.47.92.65] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 8BIT MIME-Version: 1.0 X-CFilter-Loop: Reflected Precedence: bulk List-ID: X-Mailing-List: linux-arch@vger.kernel.org > -----Original Message----- > From: Will Deacon [mailto:will@kernel.org] > Sent: 06 August 2021 12:31 > To: linux-arm-kernel@lists.infradead.org > Cc: kernel-team@android.com; Will Deacon ; Catalin > Marinas ; Marc Zyngier ; Jade > Alglave ; Shameerali Kolothum Thodi > ; kvmarm@lists.cs.columbia.edu; > linux-arch@vger.kernel.org > Subject: [PATCH 0/4] Fix racing TLBI with ASID/VMID reallocation > > Hi all, > > While reviewing Shameer's reworked VMID allocator [1] and discussing > with Marc, we spotted a race between TLB invalidation (which typically > takes an ASID or VMID argument) and reallocation of ASID/VMID for the > context being targetted. > > The first patch spells out an example with try_to_unmap_one() in a > comment, which Catalin has kindly modelled in TLA+ at [2]. > > Although I'm posting all this together for ease of review, the intention > is that the first patch will go via arm64 with the latter going via kvm. > > Cheers, > > Will > > [1] > https://lore.kernel.org/r/20210729104009.382-1-shameerali.kolothum.thodi > @huawei.com > [2] > https://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/kernel-tla.git/commi > t/ Hi Catalin, I am going through the ASID TLA+ model and in the above commit, it appears that the different ASID check(=> ActiveAsid(c1) # ActiveAsid(c2)) for the Invariant UniqueASIDActiveTask is now removed. Just wondering why that is not relevant anymore? Thanks, Shameer > Cc: Catalin Marinas > Cc: Marc Zyngier > Cc: Jade Alglave > Cc: Shameer Kolothum > Cc: > Cc: > > --->8 > > Marc Zyngier (3): > KVM: arm64: Move kern_hyp_va() usage in __load_guest_stage2() into the > callers > KVM: arm64: Convert the host S2 over to __load_guest_stage2() > KVM: arm64: Upgrade VMID accesses to {READ,WRITE}_ONCE > > Will Deacon (1): > arm64: mm: Fix TLBI vs ASID rollover > > arch/arm64/include/asm/kvm_mmu.h | 17 ++++++----- > arch/arm64/include/asm/mmu.h | 29 > ++++++++++++++++--- > arch/arm64/include/asm/tlbflush.h | 11 +++---- > arch/arm64/kvm/arm.c | 2 +- > arch/arm64/kvm/hyp/include/nvhe/mem_protect.h | 2 +- > arch/arm64/kvm/hyp/nvhe/mem_protect.c | 6 ++-- > arch/arm64/kvm/hyp/nvhe/switch.c | 4 ++- > arch/arm64/kvm/hyp/nvhe/tlb.c | 2 +- > arch/arm64/kvm/hyp/vhe/switch.c | 2 +- > arch/arm64/kvm/hyp/vhe/tlb.c | 2 +- > arch/arm64/kvm/mmu.c | 2 +- > 11 files changed, 52 insertions(+), 27 deletions(-) > > -- > 2.32.0.605.g8dce9f2422-goog 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 X-Spam-Level: X-Spam-Status: No, score=-13.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH,MAILING_LIST_MULTI, MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id EC834C433F5 for ; Fri, 10 Sep 2021 09:06:41 +0000 (UTC) Received: from mm01.cs.columbia.edu (mm01.cs.columbia.edu [128.59.11.253]) by mail.kernel.org (Postfix) with ESMTP id 43BBE6101A for ; Fri, 10 Sep 2021 09:06:41 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 43BBE6101A Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=huawei.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.cs.columbia.edu Received: from localhost (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id B2E464B186; Fri, 10 Sep 2021 05:06:40 -0400 (EDT) X-Virus-Scanned: at lists.cs.columbia.edu Received: from mm01.cs.columbia.edu ([127.0.0.1]) by localhost (mm01.cs.columbia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id hwdLB7R6Ya1g; Fri, 10 Sep 2021 05:06:39 -0400 (EDT) Received: from mm01.cs.columbia.edu (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id 962754B187; Fri, 10 Sep 2021 05:06:39 -0400 (EDT) Received: from localhost (localhost [127.0.0.1]) by mm01.cs.columbia.edu (Postfix) with ESMTP id F020F4B17E for ; Fri, 10 Sep 2021 05:06:37 -0400 (EDT) X-Virus-Scanned: at lists.cs.columbia.edu Received: from mm01.cs.columbia.edu ([127.0.0.1]) by localhost (mm01.cs.columbia.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id Tr1tgY0MYv0C for ; Fri, 10 Sep 2021 05:06:35 -0400 (EDT) Received: from frasgout.his.huawei.com (frasgout.his.huawei.com [185.176.79.56]) by mm01.cs.columbia.edu (Postfix) with ESMTPS id 329D74B116 for ; Fri, 10 Sep 2021 05:06:35 -0400 (EDT) Received: from fraeml702-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4H5VLX22N2z67hcS; Fri, 10 Sep 2021 17:04:36 +0800 (CST) Received: from lhreml715-chm.china.huawei.com (10.201.108.66) by fraeml702-chm.china.huawei.com (10.206.15.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.8; Fri, 10 Sep 2021 11:06:32 +0200 Received: from lhreml710-chm.china.huawei.com (10.201.108.61) by lhreml715-chm.china.huawei.com (10.201.108.66) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.8; Fri, 10 Sep 2021 10:06:32 +0100 Received: from lhreml710-chm.china.huawei.com ([169.254.81.184]) by lhreml710-chm.china.huawei.com ([169.254.81.184]) with mapi id 15.01.2308.008; Fri, 10 Sep 2021 10:06:31 +0100 From: Shameerali Kolothum Thodi To: Will Deacon , "linux-arm-kernel@lists.infradead.org" , Catalin Marinas Subject: RE: [PATCH 0/4] Fix racing TLBI with ASID/VMID reallocation Thread-Topic: [PATCH 0/4] Fix racing TLBI with ASID/VMID reallocation Thread-Index: AQHXiraYscBrfnIwF0OIF7R8segGVaudIb7g Date: Fri, 10 Sep 2021 09:06:31 +0000 Message-ID: <753ff5ea79d54db0af83d195adcfa2b1@huawei.com> References: <20210806113109.2475-1-will@kernel.org> In-Reply-To: <20210806113109.2475-1-will@kernel.org> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.47.92.65] MIME-Version: 1.0 X-CFilter-Loop: Reflected Cc: "linux-arch@vger.kernel.org" , Marc Zyngier , Jonathan Cameron , "kernel-team@android.com" , "kvmarm@lists.cs.columbia.edu" , Jade Alglave X-BeenThere: kvmarm@lists.cs.columbia.edu X-Mailman-Version: 2.1.14 Precedence: list List-Id: Where KVM/ARM decisions are made List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Errors-To: kvmarm-bounces@lists.cs.columbia.edu Sender: kvmarm-bounces@lists.cs.columbia.edu > -----Original Message----- > From: Will Deacon [mailto:will@kernel.org] > Sent: 06 August 2021 12:31 > To: linux-arm-kernel@lists.infradead.org > Cc: kernel-team@android.com; Will Deacon ; Catalin > Marinas ; Marc Zyngier ; Jade > Alglave ; Shameerali Kolothum Thodi > ; kvmarm@lists.cs.columbia.edu; > linux-arch@vger.kernel.org > Subject: [PATCH 0/4] Fix racing TLBI with ASID/VMID reallocation > > Hi all, > > While reviewing Shameer's reworked VMID allocator [1] and discussing > with Marc, we spotted a race between TLB invalidation (which typically > takes an ASID or VMID argument) and reallocation of ASID/VMID for the > context being targetted. > > The first patch spells out an example with try_to_unmap_one() in a > comment, which Catalin has kindly modelled in TLA+ at [2]. > > Although I'm posting all this together for ease of review, the intention > is that the first patch will go via arm64 with the latter going via kvm. > > Cheers, > > Will > > [1] > https://lore.kernel.org/r/20210729104009.382-1-shameerali.kolothum.thodi > @huawei.com > [2] > https://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/kernel-tla.git/commi > t/ Hi Catalin, I am going through the ASID TLA+ model and in the above commit, it appears that the different ASID check(=> ActiveAsid(c1) # ActiveAsid(c2)) for the Invariant UniqueASIDActiveTask is now removed. Just wondering why that is not relevant anymore? Thanks, Shameer > Cc: Catalin Marinas > Cc: Marc Zyngier > Cc: Jade Alglave > Cc: Shameer Kolothum > Cc: > Cc: > > --->8 > > Marc Zyngier (3): > KVM: arm64: Move kern_hyp_va() usage in __load_guest_stage2() into the > callers > KVM: arm64: Convert the host S2 over to __load_guest_stage2() > KVM: arm64: Upgrade VMID accesses to {READ,WRITE}_ONCE > > Will Deacon (1): > arm64: mm: Fix TLBI vs ASID rollover > > arch/arm64/include/asm/kvm_mmu.h | 17 ++++++----- > arch/arm64/include/asm/mmu.h | 29 > ++++++++++++++++--- > arch/arm64/include/asm/tlbflush.h | 11 +++---- > arch/arm64/kvm/arm.c | 2 +- > arch/arm64/kvm/hyp/include/nvhe/mem_protect.h | 2 +- > arch/arm64/kvm/hyp/nvhe/mem_protect.c | 6 ++-- > arch/arm64/kvm/hyp/nvhe/switch.c | 4 ++- > arch/arm64/kvm/hyp/nvhe/tlb.c | 2 +- > arch/arm64/kvm/hyp/vhe/switch.c | 2 +- > arch/arm64/kvm/hyp/vhe/tlb.c | 2 +- > arch/arm64/kvm/mmu.c | 2 +- > 11 files changed, 52 insertions(+), 27 deletions(-) > > -- > 2.32.0.605.g8dce9f2422-goog _______________________________________________ kvmarm mailing list kvmarm@lists.cs.columbia.edu https://lists.cs.columbia.edu/mailman/listinfo/kvmarm 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 X-Spam-Level: X-Spam-Status: No, score=-14.1 required=3.0 tests=BAYES_00,DKIMWL_WL_HIGH, DKIM_SIGNED,DKIM_VALID,HEADER_FROM_DIFFERENT_DOMAINS,INCLUDES_PATCH, MAILING_LIST_MULTI,MENTIONS_GIT_HOSTING,SPF_HELO_NONE,SPF_PASS autolearn=unavailable autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id B6F02C433EF for ; Fri, 10 Sep 2021 09:08:58 +0000 (UTC) Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 7C7B96109F for ; Fri, 10 Sep 2021 09:08:58 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 7C7B96109F Authentication-Results: mail.kernel.org; dmarc=fail (p=none dis=none) header.from=huawei.com Authentication-Results: mail.kernel.org; spf=none smtp.mailfrom=lists.infradead.org DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:MIME-Version:In-Reply-To:References: Message-ID:Date:Subject:CC:To:From:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=8mNdmzzI1ETbHhplqHMX8lExxPWEN1CDDkgjulqEje0=; b=j68pVfw5cHd9zZ CJnHJAHzuedUHFdG5GUltGM77bck9Itjd//plYMPWujMwjTwTUyGsjoBa3YPO/wYMR+9zD6mBDr8V nAi48hpZxeIHzQ2Hmvlsr7P5g8bN1vtWcXL0T40OdAYhbdkMAXRCkqwrpmm2eAKZC+41NxUmGpeUL m1f7/gB9eEJDXgF+XEsebXGgeWTntYUAdLBC96p/KnrBz41ceVf0JUUm1OPhtlrLqLlijdytHheX6 Nzx/3zz8NGPb8v86+wM1q1tuvJmGL4CUkSK2M/eXjg/2FxiXocoOkINZgIEgOaQ0UzroM35X6P89p WU+o5fcrBEYfp60Hx9AA==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1mOcUe-00CHRc-6W; Fri, 10 Sep 2021 09:06:44 +0000 Received: from frasgout.his.huawei.com ([185.176.79.56]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1mOcUZ-00CHQW-3r for linux-arm-kernel@lists.infradead.org; Fri, 10 Sep 2021 09:06:41 +0000 Received: from fraeml702-chm.china.huawei.com (unknown [172.18.147.226]) by frasgout.his.huawei.com (SkyGuard) with ESMTP id 4H5VLX22N2z67hcS; Fri, 10 Sep 2021 17:04:36 +0800 (CST) Received: from lhreml715-chm.china.huawei.com (10.201.108.66) by fraeml702-chm.china.huawei.com (10.206.15.51) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.2308.8; Fri, 10 Sep 2021 11:06:32 +0200 Received: from lhreml710-chm.china.huawei.com (10.201.108.61) by lhreml715-chm.china.huawei.com (10.201.108.66) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.2308.8; Fri, 10 Sep 2021 10:06:32 +0100 Received: from lhreml710-chm.china.huawei.com ([169.254.81.184]) by lhreml710-chm.china.huawei.com ([169.254.81.184]) with mapi id 15.01.2308.008; Fri, 10 Sep 2021 10:06:31 +0100 From: Shameerali Kolothum Thodi To: Will Deacon , "linux-arm-kernel@lists.infradead.org" , Catalin Marinas CC: "kernel-team@android.com" , Marc Zyngier , Jade Alglave , "kvmarm@lists.cs.columbia.edu" , "linux-arch@vger.kernel.org" , Jonathan Cameron Subject: RE: [PATCH 0/4] Fix racing TLBI with ASID/VMID reallocation Thread-Topic: [PATCH 0/4] Fix racing TLBI with ASID/VMID reallocation Thread-Index: AQHXiraYscBrfnIwF0OIF7R8segGVaudIb7g Date: Fri, 10 Sep 2021 09:06:31 +0000 Message-ID: <753ff5ea79d54db0af83d195adcfa2b1@huawei.com> References: <20210806113109.2475-1-will@kernel.org> In-Reply-To: <20210806113109.2475-1-will@kernel.org> Accept-Language: en-GB, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.47.92.65] MIME-Version: 1.0 X-CFilter-Loop: Reflected X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20210910_020639_499940_A520437F X-CRM114-Status: GOOD ( 15.87 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org > -----Original Message----- > From: Will Deacon [mailto:will@kernel.org] > Sent: 06 August 2021 12:31 > To: linux-arm-kernel@lists.infradead.org > Cc: kernel-team@android.com; Will Deacon ; Catalin > Marinas ; Marc Zyngier ; Jade > Alglave ; Shameerali Kolothum Thodi > ; kvmarm@lists.cs.columbia.edu; > linux-arch@vger.kernel.org > Subject: [PATCH 0/4] Fix racing TLBI with ASID/VMID reallocation > > Hi all, > > While reviewing Shameer's reworked VMID allocator [1] and discussing > with Marc, we spotted a race between TLB invalidation (which typically > takes an ASID or VMID argument) and reallocation of ASID/VMID for the > context being targetted. > > The first patch spells out an example with try_to_unmap_one() in a > comment, which Catalin has kindly modelled in TLA+ at [2]. > > Although I'm posting all this together for ease of review, the intention > is that the first patch will go via arm64 with the latter going via kvm. > > Cheers, > > Will > > [1] > https://lore.kernel.org/r/20210729104009.382-1-shameerali.kolothum.thodi > @huawei.com > [2] > https://git.kernel.org/pub/scm/linux/kernel/git/cmarinas/kernel-tla.git/commi > t/ Hi Catalin, I am going through the ASID TLA+ model and in the above commit, it appears that the different ASID check(=> ActiveAsid(c1) # ActiveAsid(c2)) for the Invariant UniqueASIDActiveTask is now removed. Just wondering why that is not relevant anymore? Thanks, Shameer > Cc: Catalin Marinas > Cc: Marc Zyngier > Cc: Jade Alglave > Cc: Shameer Kolothum > Cc: > Cc: > > --->8 > > Marc Zyngier (3): > KVM: arm64: Move kern_hyp_va() usage in __load_guest_stage2() into the > callers > KVM: arm64: Convert the host S2 over to __load_guest_stage2() > KVM: arm64: Upgrade VMID accesses to {READ,WRITE}_ONCE > > Will Deacon (1): > arm64: mm: Fix TLBI vs ASID rollover > > arch/arm64/include/asm/kvm_mmu.h | 17 ++++++----- > arch/arm64/include/asm/mmu.h | 29 > ++++++++++++++++--- > arch/arm64/include/asm/tlbflush.h | 11 +++---- > arch/arm64/kvm/arm.c | 2 +- > arch/arm64/kvm/hyp/include/nvhe/mem_protect.h | 2 +- > arch/arm64/kvm/hyp/nvhe/mem_protect.c | 6 ++-- > arch/arm64/kvm/hyp/nvhe/switch.c | 4 ++- > arch/arm64/kvm/hyp/nvhe/tlb.c | 2 +- > arch/arm64/kvm/hyp/vhe/switch.c | 2 +- > arch/arm64/kvm/hyp/vhe/tlb.c | 2 +- > arch/arm64/kvm/mmu.c | 2 +- > 11 files changed, 52 insertions(+), 27 deletions(-) > > -- > 2.32.0.605.g8dce9f2422-goog _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel