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 B8C30C433FE for ; Fri, 24 Dec 2021 04:14:39 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id F3FB26B0072; Thu, 23 Dec 2021 23:14:38 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id EF04C6B0073; Thu, 23 Dec 2021 23:14:38 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id DB9F36B0074; Thu, 23 Dec 2021 23:14:38 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from forelay.hostedemail.com (smtprelay0175.hostedemail.com [216.40.44.175]) by kanga.kvack.org (Postfix) with ESMTP id CEE336B0072 for ; Thu, 23 Dec 2021 23:14:38 -0500 (EST) Received: from smtpin23.hostedemail.com (10.5.19.251.rfc1918.com [10.5.19.251]) by forelay04.hostedemail.com (Postfix) with ESMTP id 8C6FE8A3F4 for ; Fri, 24 Dec 2021 04:14:38 +0000 (UTC) X-FDA: 78951371436.23.E60E0DA Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by imf25.hostedemail.com (Postfix) with ESMTP id 5A844A002C for ; Fri, 24 Dec 2021 04:14:27 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1640319277; x=1671855277; h=date:from:to:cc:subject:message-id:reply-to:references: mime-version:in-reply-to; bh=/49miauxNDl94xdxNi7g5SLdNpWpXmBxfwYVTy6gkAk=; b=YWa4fKgcQZxPGnRNTyB8s07MgQZkfuwikiwXnAP2NBEsp6JznX2BS+TH UNcOCQhH0hO7aMRzukxQs4S3AEOE1E8+joj9N5oxQtimXK/+wRGtv7bc5 zevb2z2nv631jl8bqGbRnOssgT7XOj7aUu+H5FZXodvbqX5uni/gXCKEU udq/xp/Dd+DMUWVG2G0e3w6Sfwb1GbZJZGLiNO55wMvcBozE6rgURgNuN 2hJFTrxn457gGJwkziuNvSvHltz54s90DlWdO12gDLWAqG/zQg2NB7387 n8hd6NBGxcfULfdJg6b8P9tgrODD6TXrivnaxTjy32mji2fXWS0HECvEx g==; X-IronPort-AV: E=McAfee;i="6200,9189,10207"; a="265139245" X-IronPort-AV: E=Sophos;i="5.88,231,1635231600"; d="scan'208";a="265139245" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga101.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 23 Dec 2021 20:14:36 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.88,231,1635231600"; d="scan'208";a="664765610" Received: from chaop.bj.intel.com (HELO localhost) ([10.240.192.101]) by fmsmga001.fm.intel.com with ESMTP; 23 Dec 2021 20:14:29 -0800 Date: Fri, 24 Dec 2021 12:13:51 +0800 From: Chao Peng To: Sean Christopherson Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-fsdevel@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 , Yu Zhang , "Kirill A . Shutemov" , luto@kernel.org, john.ji@intel.com, susie.li@intel.com, jun.nakajima@intel.com, dave.hansen@intel.com, ak@linux.intel.com, david@redhat.com Subject: Re: [PATCH v3 kvm/queue 11/16] KVM: Add kvm_map_gfn_range Message-ID: <20211224041351.GB44042@chaop.bj.intel.com> Reply-To: Chao Peng References: <20211223123011.41044-1-chao.p.peng@linux.intel.com> <20211223123011.41044-12-chao.p.peng@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Authentication-Results: imf25.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=YWa4fKgc; spf=none (imf25.hostedemail.com: domain of chao.p.peng@linux.intel.com has no SPF policy when checking 192.55.52.88) smtp.mailfrom=chao.p.peng@linux.intel.com; dmarc=pass (policy=none) header.from=intel.com X-Rspamd-Server: rspam06 X-Rspamd-Queue-Id: 5A844A002C X-Stat-Signature: 7fey5kk9stcwaoz3s1jxnygshyw1tu5c X-HE-Tag: 1640319267-921477 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, Dec 23, 2021 at 06:06:19PM +0000, Sean Christopherson wrote: > On Thu, Dec 23, 2021, Chao Peng wrote: > > This new function establishes the mapping in KVM page tables for a > > given gfn range. It can be used in the memory fallocate callback for > > memfd based memory to establish the mapping for KVM secondary MMU when > > the pages are allocated in the memory backend. > > NAK, under no circumstance should KVM install SPTEs in response to allocating > memory in a file. The correct thing to do is to invalidate the gfn range > associated with the newly mapped range, i.e. wipe out any shared SPTEs associated > with the memslot. Right, thanks.