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 kanga.kvack.org (kanga.kvack.org [205.233.56.17]) by smtp.lore.kernel.org (Postfix) with ESMTP id DB641C433EF for ; Tue, 29 Mar 2022 19:23:11 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 63C748D0002; Tue, 29 Mar 2022 15:23:11 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 5EAA98D0001; Tue, 29 Mar 2022 15:23:11 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 4B2CD8D0002; Tue, 29 Mar 2022 15:23:11 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.hostedemail.com [64.99.140.28]) by kanga.kvack.org (Postfix) with ESMTP id 3D0898D0001 for ; Tue, 29 Mar 2022 15:23:11 -0400 (EDT) Received: from smtpin06.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay08.hostedemail.com (Postfix) with ESMTP id 1577821AB2 for ; Tue, 29 Mar 2022 19:23:11 +0000 (UTC) X-FDA: 79298396982.06.F8378E8 Received: from mail-pf1-f181.google.com (mail-pf1-f181.google.com [209.85.210.181]) by imf03.hostedemail.com (Postfix) with ESMTP id 9536A20004 for ; Tue, 29 Mar 2022 19:23:10 +0000 (UTC) Received: by mail-pf1-f181.google.com with SMTP id w7so14073251pfu.11 for ; Tue, 29 Mar 2022 12:23:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20210112; h=date:from:to:cc:subject:message-id:references:mime-version :content-disposition:in-reply-to; bh=leHL94h+MpS4/OEOPtJEdh0aJz+CrPTMrBVs83Qfv3E=; b=f9RP67uwP/U4yYMwWleoqNxKjYfD+VZ9bI5mxhlSyD+CCMlJ5FCF77eVp5wFXeZEON V2IkeIbb0iHzwsqI2Do5dROL5K53gUBZaDEYt42cPjujky5xN1evllqzZccVhRjtEiQc BtFaX3WWMuJUXnlj4vHNmqhdRoF82wpMpPdh3QXX4XHcC1vsLHj9RZKCIyFRbJXDEpb4 6grrlWOCR3R9b9US42EBjL5V5jC63ILxWOO/exIV0gi7WqmoC2YAHWbBTYwrE7uxi8LY nvZYtSC+jvXOJc6q3t8LNy6rdjjy8WQl8/HONzcHWfFl4cAyGvjbsH3Nd/l/9l36p+7v Jaqg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:date:from:to:cc:subject:message-id:references :mime-version:content-disposition:in-reply-to; bh=leHL94h+MpS4/OEOPtJEdh0aJz+CrPTMrBVs83Qfv3E=; b=ykUmq7XpPc8r+vJc4JTxB6p1HhWtIwiXkwCKbjP2/jm91sZUlR7leCaJGJdBzFVzQ0 OhZcUqvzDVW8xioPz251hGCp39QeZEMzRw+K+3g/sDHCKHMILMmV6muAT28LM++MC95M cWPgm3fZZk6GNl9k0Z7t/4EzwcgppY/EdXbLIXLv99Wqqo3V0B6uUQbaXFBc47Nj9bZi voUUapbJo4UsWdoxTJfX2dvgBRUmGY0QebO47wrt2TO8Veo0QOKCIiOKDM1rx1ryF9oX JvHAkpcme6AHAxGRw+ioPzdOfhlBPW1kabt7DGqnw8svT/wxKI/WQSG6DQiI88UdstNM 16rg== X-Gm-Message-State: AOAM530B29ruh79qb8qfiSnOLNl8hVEVLT5mCaK7Pugn5KadCZi1tI8t siphQ65F+qZDf27udA7DiAd3gg== X-Google-Smtp-Source: ABdhPJwjnUern9b0nwzFDfrc+KHUoi+vzEO/eEg7u0tJsu4zhLLogQOi1j9Ecq4LcoDSrQKd/DUgkw== X-Received: by 2002:a05:6a00:1908:b0:4f7:8813:b2cb with SMTP id y8-20020a056a00190800b004f78813b2cbmr28993474pfi.54.1648581789396; Tue, 29 Mar 2022 12:23:09 -0700 (PDT) Received: from google.com (157.214.185.35.bc.googleusercontent.com. [35.185.214.157]) by smtp.gmail.com with ESMTPSA id j6-20020a17090a588600b001c699d77503sm3584376pji.2.2022.03.29.12.23.08 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 29 Mar 2022 12:23:08 -0700 (PDT) Date: Tue, 29 Mar 2022 19:23:04 +0000 From: Sean Christopherson To: Chao Peng Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, linux-api@vger.kernel.org, qemu-devel@nongnu.org, Paolo Bonzini , Jonathan Corbet , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , Thomas Gleixner , Ingo Molnar , Borislav Petkov , x86@kernel.org, "H . Peter Anvin" , Hugh Dickins , Jeff Layton , "J . Bruce Fields" , Andrew Morton , Mike Rapoport , Steven Price , "Maciej S . Szmigiero" , Vlastimil Babka , Vishal Annapurve , Yu Zhang , "Kirill A . Shutemov" , luto@kernel.org, jun.nakajima@intel.com, dave.hansen@intel.com, ak@linux.intel.com, david@redhat.com Subject: Re: [PATCH v5 11/13] KVM: Zap existing KVM mappings when pages changed in the private fd Message-ID: References: <20220310140911.50924-1-chao.p.peng@linux.intel.com> <20220310140911.50924-12-chao.p.peng@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20220310140911.50924-12-chao.p.peng@linux.intel.com> Authentication-Results: imf03.hostedemail.com; dkim=pass header.d=google.com header.s=20210112 header.b=f9RP67uw; spf=pass (imf03.hostedemail.com: domain of seanjc@google.com designates 209.85.210.181 as permitted sender) smtp.mailfrom=seanjc@google.com; dmarc=pass (policy=reject) header.from=google.com X-Rspam-User: X-Rspamd-Server: rspam10 X-Rspamd-Queue-Id: 9536A20004 X-Stat-Signature: u91ju5tq1ycsmh8r3674kw16yej47xq8 X-HE-Tag: 1648581790-880367 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 Sender: owner-linux-mm@kvack.org Precedence: bulk X-Loop: owner-majordomo@kvack.org List-ID: On Thu, Mar 10, 2022, Chao Peng wrote: > diff --git a/virt/kvm/kvm_main.c b/virt/kvm/kvm_main.c > index 67349421eae3..52319f49d58a 100644 > --- a/virt/kvm/kvm_main.c > +++ b/virt/kvm/kvm_main.c > @@ -841,8 +841,43 @@ static int kvm_init_mmu_notifier(struct kvm *kvm) > #endif /* CONFIG_MMU_NOTIFIER && KVM_ARCH_WANT_MMU_NOTIFIER */ > > #ifdef CONFIG_MEMFILE_NOTIFIER > +static void kvm_memfile_notifier_handler(struct memfile_notifier *notifier, > + pgoff_t start, pgoff_t end) > +{ > + int idx; > + struct kvm_memory_slot *slot = container_of(notifier, > + struct kvm_memory_slot, > + notifier); > + struct kvm_gfn_range gfn_range = { > + .slot = slot, > + .start = start - (slot->private_offset >> PAGE_SHIFT), > + .end = end - (slot->private_offset >> PAGE_SHIFT), > + .may_block = true, > + }; > + struct kvm *kvm = slot->kvm; > + > + gfn_range.start = max(gfn_range.start, slot->base_gfn); > + gfn_range.end = min(gfn_range.end, slot->base_gfn + slot->npages); > + > + if (gfn_range.start >= gfn_range.end) > + return; > + > + idx = srcu_read_lock(&kvm->srcu); > + KVM_MMU_LOCK(kvm); > + kvm_unmap_gfn_range(kvm, &gfn_range); > + kvm_flush_remote_tlbs(kvm); This should check the result of kvm_unmap_gfn_range() and flush only if necessary. kvm->mmu_notifier_seq needs to be incremented, otherwise KVM will incorrectly install a SPTE if the mapping is zapped between retrieving the pfn in faultin and installing it after acquire mmu_lock. > + KVM_MMU_UNLOCK(kvm); > + srcu_read_unlock(&kvm->srcu, idx); > +} > + > +static struct memfile_notifier_ops kvm_memfile_notifier_ops = { > + .invalidate = kvm_memfile_notifier_handler, > + .fallocate = kvm_memfile_notifier_handler, > +}; > + > static inline int kvm_memfile_register(struct kvm_memory_slot *slot) > { > + slot->notifier.ops = &kvm_memfile_notifier_ops; > return memfile_register_notifier(file_inode(slot->private_file), > &slot->notifier, > &slot->pfn_ops); > @@ -1963,6 +1998,7 @@ int __kvm_set_memory_region(struct kvm *kvm, > new->private_file = file; > new->private_offset = mem->flags & KVM_MEM_PRIVATE ? > region_ext->private_offset : 0; > + new->kvm = kvm; > > r = kvm_set_memslot(kvm, old, new, change); > if (!r) > -- > 2.17.1 >