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 20F2FC10F31 for ; Tue, 13 Dec 2022 12:04:39 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 809B58E0003; Tue, 13 Dec 2022 07:04:38 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id 792D68E0002; Tue, 13 Dec 2022 07:04:38 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 60C618E0003; Tue, 13 Dec 2022 07:04:38 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0015.hostedemail.com [216.40.44.15]) by kanga.kvack.org (Postfix) with ESMTP id 4CEEC8E0002 for ; Tue, 13 Dec 2022 07:04:38 -0500 (EST) Received: from smtpin02.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay10.hostedemail.com (Postfix) with ESMTP id 0848BC0A81 for ; Tue, 13 Dec 2022 12:04:38 +0000 (UTC) X-FDA: 80237151036.02.D1D12F4 Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by imf03.hostedemail.com (Postfix) with ESMTP id 2C12120007 for ; Tue, 13 Dec 2022 12:04:33 +0000 (UTC) Authentication-Results: imf03.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=ICo+zjRY; spf=pass (imf03.hostedemail.com: domain of xiaoyao.li@intel.com designates 192.55.52.93 as permitted sender) smtp.mailfrom=xiaoyao.li@intel.com; dmarc=pass (policy=none) header.from=intel.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1670933075; h=from:from:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references:dkim-signature; bh=8sa8MYdJza1TZG8FrrfXadf8YfOY6tbvJqlqAmBN0Yk=; b=bWlz2Q4vU9CQoT16akE02HbHYCeXcGCP+bqPGFUjjJUAsexy/rSdtIegy8ge45WEfXEqY9 ysevwC+zuYw1QJcA4GMVBb8t2lEt+lIiGudjj/g50/Wfxi+Fe2qxggeVFORWOizbbUv3ar yzFmDoY3GuP//McrZ7ntue1YDltj0O8= ARC-Authentication-Results: i=1; imf03.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=ICo+zjRY; spf=pass (imf03.hostedemail.com: domain of xiaoyao.li@intel.com designates 192.55.52.93 as permitted sender) smtp.mailfrom=xiaoyao.li@intel.com; dmarc=pass (policy=none) header.from=intel.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1670933075; a=rsa-sha256; cv=none; b=mvwmc9sTv6V8uH6IAqf693zvRLdckAunjh4t1O0kr1VzouheZeo4aPnywkGgzdTfv4SdGd FmojBX/JyJB/ngyWap1OIs+Zl0bm2v58hqOBH/hZr8hkvmeaOohXnboLEuHfwSqKayC0Cs 1wshvZx7SXxL4sPZpD2Tr8j/eoWhYoA= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1670933074; x=1702469074; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=Mmu9iz+w3ikTp4SbfrscqkeC55Id70T9EZSgNrTlufI=; b=ICo+zjRYU9Df9v1+MBgoEnQCrbeHgynQd751IQZFVlmfLgDOvKJ3d4qW zJerR6CMUzoKJ4xUpChCTqFOmhMJf6hq8ov3+vi3xP0a4RuCyiAHiQcjX B34fYcJCB6PxV9XckyBOWRB+5NpNBBe6bxzudwkQq4C11vIHgaJpKaR6k riLFLrOkVoSMjHWIj9T4imrePq6ia3fd8lzgFDD9zxzMmMA+yynCZVCNY N8y5xjY/20FjqtfvsPGxmzG0y1XWgrykd+f72387W/MO4P503FH1rnRJh wth6QhpEoVP93g8RMn0ICFXriKmn15Wm34levyHRab47D0+rABGg5F6bL A==; X-IronPort-AV: E=McAfee;i="6500,9779,10559"; a="315751843" X-IronPort-AV: E=Sophos;i="5.96,241,1665471600"; d="scan'208";a="315751843" Received: from orsmga003.jf.intel.com ([10.7.209.27]) by fmsmga102.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Dec 2022 04:04:30 -0800 X-IronPort-AV: E=McAfee;i="6500,9779,10559"; a="598800801" X-IronPort-AV: E=Sophos;i="5.96,241,1665471600"; d="scan'208";a="598800801" Received: from xiaoyaol-hp-g830.ccr.corp.intel.com (HELO [10.255.31.20]) ([10.255.31.20]) by orsmga003-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 13 Dec 2022 04:04:17 -0800 Message-ID: <4d736cc0-f249-6531-c0af-7093c2c2537f@intel.com> Date: Tue, 13 Dec 2022 20:04:14 +0800 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Firefox/102.0 Thunderbird/102.5.1 Subject: Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory Content-Language: en-US To: Chao Peng Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org, linux-mm@kvack.org, linux-fsdevel@vger.kernel.org, linux-arch@vger.kernel.org, linux-api@vger.kernel.org, linux-doc@vger.kernel.org, qemu-devel@nongnu.org, Paolo Bonzini , Jonathan Corbet , Sean Christopherson , Vitaly Kuznetsov , Wanpeng Li , Jim Mattson , Joerg Roedel , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Arnd Bergmann , Naoya Horiguchi , Miaohe Lin , x86@kernel.org, "H . Peter Anvin" , Hugh Dickins , Jeff Layton , "J . Bruce Fields" , Andrew Morton , Shuah Khan , 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, aarcange@redhat.com, ddutile@redhat.com, dhildenb@redhat.com, Quentin Perret , tabba@google.com, Michael Roth , mhocko@suse.com, wei.w.wang@intel.com References: <20221202061347.1070246-1-chao.p.peng@linux.intel.com> <20221202061347.1070246-4-chao.p.peng@linux.intel.com> <20221208113003.GE1304936@chaop.bj.intel.com> From: Xiaoyao Li In-Reply-To: <20221208113003.GE1304936@chaop.bj.intel.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspam-User: X-Rspamd-Server: rspam04 X-Rspamd-Queue-Id: 2C12120007 X-Stat-Signature: rz1ud65efgihcc6tpueriuwhppwz5b1o X-HE-Tag: 1670933073-618024 X-HE-Meta: U2FsdGVkX1+HEi5yIY4c1FGv16Du1Ab+kmAvGYCS9kCnnm66c9Ii9Azlw7NU75Qh83yXI+MceA+v3oCBDKvGOJP5sBCyWw9lEYHpd5UMu0Lb6j+9FcvNbHpa6EqYp/1uA9STdD1IbFycFYXr28ELgoEqsfJYcMzGj9IA8J2aVDo1IXFZYEFWswQ1BIITEkHZBH/3WkLjjnyiJ6O4cuBYbEnRhjHnEd/nvW5uTV4aHVOR4YOVEveL/mqPHAj6p+TjkMI3wgth6PjwxSmnaJp4QLSsSMDfyl83hAz84B02zykFw02CujUlrqbWdmP0a6K42e0merS+JvdQbwpWayBRq20TPnX9o3g8yzUgpusplRfXYQ6p9yMGfxs44XtymxXgVvB+PYMDA+pzSLlArzs+cjp6E/8e6JLRvRHsP+SPmfqcbYF0iiRP4E2zHQczLnYX1WSQkGWtXDG3JH3JyDULjmdve5CswJ+Nxvrd30G+GCCf3Jp0qSqIXQ5rTy1KgnYf8urZ+805x1DK/QcOyAF7+UaENnDJc0m5ikXci0Ct8vyQynxvJZ7ZJOI5BBIWhSTUpns4H3CEE2E/Ri802CrjgzlVBjKepzc8dnHajiV8bdaCEkrUEU4fymWNH7k8ECj3mf1JXwr8Qo45ibj5++aEj5T6GLJzxzZwDqN1JIA2Y2FjvCYC93GpxOwbf6qXC7FGMT3IaEizMS1Po6BFyMLX9KMhVRX3hKXOgGD64gf3bpL9eB1aqVoutmi/sL5YlmshWREARvj9DuaeXmUnYK9Qw5MR4T0Lru6vl9Z6neQoWGYbWuFcz2NZyt7m+qT6YLyVWk+EgahsHOBdvjqi4E04JdcFY47cIF2MZfbpM9DPcvE= 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 12/8/2022 7:30 PM, Chao Peng wrote: > On Thu, Dec 08, 2022 at 04:37:03PM +0800, Xiaoyao Li wrote: >> On 12/2/2022 2:13 PM, Chao Peng wrote: >> >> .. >> >>> Together with the change, a new config HAVE_KVM_RESTRICTED_MEM is added >>> and right now it is selected on X86_64 only. >>> >> >> From the patch implementation, I have no idea why HAVE_KVM_RESTRICTED_MEM is >> needed. > > The reason is we want KVM further controls the feature enabling. An > opt-in CONFIG_RESTRICTEDMEM can cause problem if user sets that for > unsupported architectures. HAVE_KVM_RESTRICTED_MEM is not used in this patch. It's better to introduce it in the patch that actually uses it. > Here is the original discussion: > https://lore.kernel.org/all/YkJLFu98hZOvTSrL@google.com/ > > Thanks, > Chao