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 39228C83F27 for ; Wed, 16 Jul 2025 04:09:06 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id A5AF86B0092; Wed, 16 Jul 2025 00:09:05 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id A32936B0093; Wed, 16 Jul 2025 00:09:05 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 96F7D6B0095; Wed, 16 Jul 2025 00:09:05 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0014.hostedemail.com [216.40.44.14]) by kanga.kvack.org (Postfix) with ESMTP id 88CF86B0092 for ; Wed, 16 Jul 2025 00:09:05 -0400 (EDT) Received: from smtpin20.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay07.hostedemail.com (Postfix) with ESMTP id 15EF3160272 for ; Wed, 16 Jul 2025 04:09:05 +0000 (UTC) X-FDA: 83668797450.20.AD1B570 Received: from mgamail.intel.com (mgamail.intel.com [192.198.163.15]) by imf16.hostedemail.com (Postfix) with ESMTP id 51BAF180009 for ; Wed, 16 Jul 2025 04:09:02 +0000 (UTC) Authentication-Results: imf16.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=gMysBm6I; dmarc=pass (policy=none) header.from=intel.com; spf=pass (imf16.hostedemail.com: domain of xiaoyao.li@intel.com designates 192.198.163.15 as permitted sender) smtp.mailfrom=xiaoyao.li@intel.com ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=hostedemail.com; s=arc-20220608; t=1752638943; 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=wiupQNPPRjxnjTlLMY8fKXFAPNGhcpnQTy4d5G3eZFY=; b=MoX0o8k3tfjWdyN02deJxdncUclpO5Xrl5KR4Xop3t50V/Dq6ZEQBBSocQEI0tqXXOQwW6 /shMrfy6elJPRnnJod2b+rFJmQPqBpTI8DvuvCE711Fi0Sq0Eo1QhLDqMLgUZoFmDk7gJU yz1is/TiL3T1Wuja2XzZmF0PHCOKwB0= ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1752638943; a=rsa-sha256; cv=none; b=JngmMSyuEneCB5uHUstT3zJ7mi5/+LGq3g0TmfkJqMgECGAid01DouQvptSrGEhWuoeNGu 0RsO7SYcpcnEWrmaqVxWsDDf5FH9bGW6homvuytwNp88xDIsiAw9Z326xcNkmEd8MJ5868 iIGaupGQn0r4TxKo2XXqlisy4l4JNDY= ARC-Authentication-Results: i=1; imf16.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=gMysBm6I; dmarc=pass (policy=none) header.from=intel.com; spf=pass (imf16.hostedemail.com: domain of xiaoyao.li@intel.com designates 192.198.163.15 as permitted sender) smtp.mailfrom=xiaoyao.li@intel.com DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1752638942; x=1784174942; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=HgzFa1xmLCqd7SiqxwPlH23pvguIpjfNfvSPSfglfnc=; b=gMysBm6IHb8D/65gtp1133bFxmLgUy0j0OIWemvsKJgs6cV+8jVmtOJc nKLJrdqUnnnq56ximyl0oiLodxNWNPOjAlmXPN/Hm8/1Hom2/i7rR4ZWf OZYo05uZkxIvvY9d0QglcR5xp7rkCi3cXHsETn81x0WSnBW5sjmeAA7ks QUdiQHPG3yjv6E1YahhJbAdVaYCLrEt63Xz4uq0vqifOW6qBuu/UH0Kv0 0C7Y7IS6k2ETQv4QFzy4Gg+yqk7nzybGFinghGti9f1PbNxno7TnnUd9r 03DDSDt4pDvwALD7vTkYAhv/eCoFWoZ4tFAa0ZRFABTiwOxxztiC3sXmE g==; X-CSE-ConnectionGUID: iiwWJA7OST6w5ZONIhgqkw== X-CSE-MsgGUID: n+/o5QUPQjuk0eeZGf+ZmA== X-IronPort-AV: E=McAfee;i="6800,10657,11493"; a="55023492" X-IronPort-AV: E=Sophos;i="6.16,315,1744095600"; d="scan'208";a="55023492" Received: from fmviesa004.fm.intel.com ([10.60.135.144]) by fmvoesa109.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Jul 2025 21:09:00 -0700 X-CSE-ConnectionGUID: AzIyrgphT4iDuvN4WCqAHQ== X-CSE-MsgGUID: qhm7N5zmQuuzHyzKWfIQMA== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.16,315,1744095600"; d="scan'208";a="162938430" Received: from xiaoyaol-hp-g830.ccr.corp.intel.com (HELO [10.124.247.1]) ([10.124.247.1]) by fmviesa004-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 15 Jul 2025 21:08:45 -0700 Message-ID: Date: Wed, 16 Jul 2025 12:08:42 +0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v14 02/21] KVM: Rename CONFIG_KVM_GENERIC_PRIVATE_MEM to CONFIG_KVM_GENERIC_GMEM_POPULATE To: Fuad Tabba , kvm@vger.kernel.org, linux-arm-msm@vger.kernel.org, linux-mm@kvack.org, kvmarm@lists.linux.dev Cc: pbonzini@redhat.com, chenhuacai@kernel.org, mpe@ellerman.id.au, anup@brainfault.org, paul.walmsley@sifive.com, palmer@dabbelt.com, aou@eecs.berkeley.edu, seanjc@google.com, viro@zeniv.linux.org.uk, brauner@kernel.org, willy@infradead.org, akpm@linux-foundation.org, yilun.xu@intel.com, chao.p.peng@linux.intel.com, jarkko@kernel.org, amoorthy@google.com, dmatlack@google.com, isaku.yamahata@intel.com, mic@digikod.net, vbabka@suse.cz, vannapurve@google.com, ackerleytng@google.com, mail@maciej.szmigiero.name, david@redhat.com, michael.roth@amd.com, wei.w.wang@intel.com, liam.merwick@oracle.com, isaku.yamahata@gmail.com, kirill.shutemov@linux.intel.com, suzuki.poulose@arm.com, steven.price@arm.com, quic_eberman@quicinc.com, quic_mnalajal@quicinc.com, quic_tsoni@quicinc.com, quic_svaddagi@quicinc.com, quic_cvanscha@quicinc.com, quic_pderrin@quicinc.com, quic_pheragu@quicinc.com, catalin.marinas@arm.com, james.morse@arm.com, yuzenghui@huawei.com, oliver.upton@linux.dev, maz@kernel.org, will@kernel.org, qperret@google.com, keirf@google.com, roypat@amazon.co.uk, shuah@kernel.org, hch@infradead.org, jgg@nvidia.com, rientjes@google.com, jhubbard@nvidia.com, fvdl@google.com, hughd@google.com, jthoughton@google.com, peterx@redhat.com, pankaj.gupta@amd.com, ira.weiny@intel.com References: <20250715093350.2584932-1-tabba@google.com> <20250715093350.2584932-3-tabba@google.com> Content-Language: en-US From: Xiaoyao Li In-Reply-To: <20250715093350.2584932-3-tabba@google.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Stat-Signature: smi78cpzn5ny97hxrnfsptppq5mecqor X-Rspamd-Queue-Id: 51BAF180009 X-Rspamd-Server: rspam10 X-Rspam-User: X-HE-Tag: 1752638942-154665 X-HE-Meta: U2FsdGVkX1+RzeG8MPZp9cmdDjmt3kLqbq0JHLCq7Ipl/HbJVr7N0puh5RCKHpID5ndhsnAAqPDxVxtdV+6TAlMwjYw9OuO56sY+NzCwtBHdnEPZG9j6XmZsPCTI5+QJTukPYb3y/0AG0Ia0I9AKdPmNFvETZLz+9lgYodvDCMv5vK786tDpSsoPMZC8hx6hLPCY1c4kWM70OH83Fqu+hwzwS/59xx+CCccMjowxYU5WejyUpaLnCcI1KKf3CnOrTPfs/nGNbXVtMMrr+cM+IxzJmONqkHWPZiutDo1EzA1gs86Vt4ju2ZZxqSdLaHZAT7XwiHB6zvUKFHnxaPWdlhnkRE0h6l/AJp2eqO2V0y/5MThhjD9Q0bsgBC5JsiO+QKz8DxTZDU4lNR+5RXv7FbLS+9d+H5++VqXSiAeiRO8Z2kCoWx4ATvUDtV59qTZp1uphwQ860pJ1ox/PDWIaTUfte1rDFTS2ZY0zEUlw0Nc6za5MZCGfomaLtN074js4JXRCYXs/lUT6dI73WBYk1nP9H54SRc+d4rO249oI9iGxH+uwO+f8JywzTjQdqQd8yIz+LFfDqkdc1CoMsCFUMFNtY9t1RgxFG+Z1Ldoi02pJuuIeDKbgyknffR838xyENy9dchmTFPAU3Gq4AM5RLHpfrFa8YklPz6umHco+cc5ntqXZzDDCEnjLks+p2mbqXRODdkbhMUM/eXwAxO1gqiXPrAsT9r0U/cuoFKrhLzpYfpoIT8uv0f4qNc4Iu6TBUMZ32lBpjNRw0lKymXlDFKkFGAGwUMiEO+nFSJqGAerHwMLRNlH3v56rn9bEzABvgK7JwHmAqf6nBBH5mok4apv40fNH7ULpczJsoXBiMflNCLD0DHLSLrWHLgIrKFCi4TdU6MzSXAkFW/lNn+kxEnsRQbybuB8iVjj296DuqwqY0LJGtrnkdCup0qpuaL1xhXYgWAwM9a5N+5DNjLO QofS05tk VWToPFcXGIBL1vU8jr4kQWQ5Pp0FXMX2iEXkYuC0VyoUW5NDK13pbLKSTy4WBJwz1KOsf4ecng3jCBGDPgqnMy29GqjELsefXeCusdBhcbR+Ph5p71VLpk6vPeDmHKWl4n0XHt2H23FxB/VH11s98o3XCX6L9GPFB214aC756onVtPT8n6s98AMliVn1JhxO9xYfWjCcvflSF5+pi4tS9ENC4WNTG0IPkgAnuMOvV/9t30mwOQmZjbMnpREE7vtPdwoSPl7Ug2x8RYE8R92J5N4D5cyGTsDOYyZPZ38noOhK9rOCWRpoynMVqt52la87CMmYn0nBWGfK4drmPtlRfopEVGZddKAw2l86gU3+c1y/Glrag3UDl4vMtKg== 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: List-Subscribe: List-Unsubscribe: On 7/15/2025 5:33 PM, Fuad Tabba wrote: > The original name was vague regarding its functionality. This Kconfig > option specifically enables and gates the kvm_gmem_populate() function, > which is responsible for populating a GPA range with guest data. Well, I disagree. The config KVM_GENERIC_PRIVATE_MEM was introduced by commit 89ea60c2c7b5 ("KVM: x86: Add support for "protected VMs" that can utilize private memory"), which is a convenient config for vm types that requires private memory support, e.g., SNP, TDX, and KVM_X86_SW_PROTECTED_VM. It was commit e4ee54479273 ("KVM: guest_memfd: let kvm_gmem_populate() operate only on private gfns") that started to use CONFIG_KVM_GENERIC_PRIVATE_MEM gates kvm_gmem_populate() function. But CONFIG_KVM_GENERIC_PRIVATE_MEM is not for kvm_gmem_populate() only. If using CONFIG_KVM_GENERIC_PRIVATE_MEM to gate kvm_gmem_populate() is vague and confusing, we can introduce KVM_GENERIC_GMEM_POPULATE to gate kvm_gmem_populate() and select KVM_GENERIC_GMEM_POPULATE under CONFIG_KVM_GENERIC_PRIVATE_MEM. Directly replace CONFIG_KVM_GENERIC_PRIVATE_MEM with KVM_GENERIC_GMEM_POPULATE doesn't look correct to me. > The new name, KVM_GENERIC_GMEM_POPULATE, describes the purpose of the > option: to enable generic guest_memfd population mechanisms. This > improves clarity for developers and ensures the name accurately reflects > the functionality it controls, especially as guest_memfd support expands > beyond purely "private" memory scenarios. > > Reviewed-by: Ira Weiny > Reviewed-by: Gavin Shan > Reviewed-by: Shivank Garg > Reviewed-by: Vlastimil Babka > Co-developed-by: David Hildenbrand > Signed-off-by: David Hildenbrand > Signed-off-by: Fuad Tabba > --- > arch/x86/kvm/Kconfig | 6 +++--- > include/linux/kvm_host.h | 2 +- > virt/kvm/Kconfig | 2 +- > virt/kvm/guest_memfd.c | 2 +- > 4 files changed, 6 insertions(+), 6 deletions(-) > > diff --git a/arch/x86/kvm/Kconfig b/arch/x86/kvm/Kconfig > index 2eeffcec5382..df1fdbb4024b 100644 > --- a/arch/x86/kvm/Kconfig > +++ b/arch/x86/kvm/Kconfig > @@ -46,7 +46,7 @@ config KVM_X86 > select HAVE_KVM_PM_NOTIFIER if PM > select KVM_GENERIC_HARDWARE_ENABLING > select KVM_GENERIC_PRE_FAULT_MEMORY > - select KVM_GENERIC_PRIVATE_MEM if KVM_SW_PROTECTED_VM > + select KVM_GENERIC_GMEM_POPULATE if KVM_SW_PROTECTED_VM > select KVM_WERROR if WERROR > > config KVM > @@ -95,7 +95,7 @@ config KVM_SW_PROTECTED_VM > config KVM_INTEL > tristate "KVM for Intel (and compatible) processors support" > depends on KVM && IA32_FEAT_CTL > - select KVM_GENERIC_PRIVATE_MEM if INTEL_TDX_HOST > + select KVM_GENERIC_GMEM_POPULATE if INTEL_TDX_HOST > select KVM_GENERIC_MEMORY_ATTRIBUTES if INTEL_TDX_HOST > help > Provides support for KVM on processors equipped with Intel's VT > @@ -157,7 +157,7 @@ config KVM_AMD_SEV > depends on KVM_AMD && X86_64 > depends on CRYPTO_DEV_SP_PSP && !(KVM_AMD=y && CRYPTO_DEV_CCP_DD=m) > select ARCH_HAS_CC_PLATFORM > - select KVM_GENERIC_PRIVATE_MEM > + select KVM_GENERIC_GMEM_POPULATE > select HAVE_KVM_ARCH_GMEM_PREPARE > select HAVE_KVM_ARCH_GMEM_INVALIDATE > help > diff --git a/include/linux/kvm_host.h b/include/linux/kvm_host.h > index 755b09dcafce..359baaae5e9f 100644 > --- a/include/linux/kvm_host.h > +++ b/include/linux/kvm_host.h > @@ -2556,7 +2556,7 @@ static inline int kvm_gmem_get_pfn(struct kvm *kvm, > int kvm_arch_gmem_prepare(struct kvm *kvm, gfn_t gfn, kvm_pfn_t pfn, int max_order); > #endif > > -#ifdef CONFIG_KVM_GENERIC_PRIVATE_MEM > +#ifdef CONFIG_KVM_GENERIC_GMEM_POPULATE > /** > * kvm_gmem_populate() - Populate/prepare a GPA range with guest data > * > diff --git a/virt/kvm/Kconfig b/virt/kvm/Kconfig > index 49df4e32bff7..559c93ad90be 100644 > --- a/virt/kvm/Kconfig > +++ b/virt/kvm/Kconfig > @@ -116,7 +116,7 @@ config KVM_GMEM > select XARRAY_MULTI > bool > > -config KVM_GENERIC_PRIVATE_MEM > +config KVM_GENERIC_GMEM_POPULATE > select KVM_GENERIC_MEMORY_ATTRIBUTES > select KVM_GMEM > bool > diff --git a/virt/kvm/guest_memfd.c b/virt/kvm/guest_memfd.c > index b2aa6bf24d3a..befea51bbc75 100644 > --- a/virt/kvm/guest_memfd.c > +++ b/virt/kvm/guest_memfd.c > @@ -638,7 +638,7 @@ int kvm_gmem_get_pfn(struct kvm *kvm, struct kvm_memory_slot *slot, > } > EXPORT_SYMBOL_GPL(kvm_gmem_get_pfn); > > -#ifdef CONFIG_KVM_GENERIC_PRIVATE_MEM > +#ifdef CONFIG_KVM_GENERIC_GMEM_POPULATE > long kvm_gmem_populate(struct kvm *kvm, gfn_t start_gfn, void __user *src, long npages, > kvm_gmem_populate_cb post_populate, void *opaque) > {