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 CC910C83F1A for ; Fri, 18 Jul 2025 06:14:42 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 6766B6B009D; Fri, 18 Jul 2025 02:14:42 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id 61FF66B009E; Fri, 18 Jul 2025 02:14:42 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id 50F2A6B009F; Fri, 18 Jul 2025 02:14:42 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0016.hostedemail.com [216.40.44.16]) by kanga.kvack.org (Postfix) with ESMTP id 3EE596B009D for ; Fri, 18 Jul 2025 02:14:42 -0400 (EDT) Received: from smtpin24.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay02.hostedemail.com (Postfix) with ESMTP id F291612DE15 for ; Fri, 18 Jul 2025 06:14:41 +0000 (UTC) X-FDA: 83676371562.24.FC423F4 Received: from mgamail.intel.com (mgamail.intel.com [198.175.65.18]) by imf30.hostedemail.com (Postfix) with ESMTP id 64ABE80002 for ; Fri, 18 Jul 2025 06:14:39 +0000 (UTC) Authentication-Results: imf30.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b="M6nO3G/q"; dmarc=pass (policy=none) header.from=intel.com; spf=pass (imf30.hostedemail.com: domain of xiaoyao.li@intel.com designates 198.175.65.18 as permitted sender) smtp.mailfrom=xiaoyao.li@intel.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1752819280; a=rsa-sha256; cv=none; b=AZwGFjpVcVQjSBKz9nYUA2psge22AXQ7wy9DTh3uO1PehUj0bwXYLqZBzwMPU5Z902Bm48 VDleAxggaXf3siTsTjp9vqISgTE+mXvwxj23Q1Lx8z8cEuliHejfyuzfX+lokYOiqxh1b+ 8lW2U5ydov7tlWmnorZjkGNhd37uU+w= ARC-Authentication-Results: i=1; imf30.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b="M6nO3G/q"; dmarc=pass (policy=none) header.from=intel.com; spf=pass (imf30.hostedemail.com: domain of xiaoyao.li@intel.com designates 198.175.65.18 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=1752819280; 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=ct+PeuKgiFpDblVS7S96JVye08F/ihJiKCK46mVNMdQ=; b=r8pfEq2n1DAeDojUm4Y1/GyQ6ooBe+p9VqrpN5QiYoJwQzURSfB5jLF6T97zbwUZNLYz4g uAx6jE4aLfNd68Mqqywoua5RoSRPfg3jymewTqGfjdujnzZ9yRC7BjuTufP3O5DG+815Cd 82yDtL5EljPBJlJEEym53+ZH6Rtph9o= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1752819281; x=1784355281; h=message-id:date:mime-version:subject:to:cc:references: from:in-reply-to:content-transfer-encoding; bh=XcJZ6mYKjvZl9/FELeN8l47ZXRZ5CIivhly0oeD5djo=; b=M6nO3G/qJht5LP13Lsu0S4rx0c7MQKs7q5UF4v4l0X1Nv+WKWE3jBdeq BtBfyN0Egv2l0LX765op0+slrAM3vHqtAVao1AkN0n1TpTA6a78GwbrWZ oLfQREuggHJJSZkwyy/c7zcbvtYSveLsqAVvBLoa8fEVn1eR5SsBY+yQO FFtW/SOfe9VHmkZgNOXVZATt1H8gHVL0/48CZUK/qiqFZOesaQNe2cWhT m9kB9s7uA75VsIC3rkero9gSevhsPxpuIGx+/GbVPU7F4hIv/W+k0bkdv EGFrJI656EtXsl6PxUkunP/SGgDqGics0QOW4Pmp817zzr/kBq4PPQSMW Q==; X-CSE-ConnectionGUID: XFnI4oSCQtShwbkP3wJwTg== X-CSE-MsgGUID: Jcdl2dahSLK80XksGG4jXA== X-IronPort-AV: E=McAfee;i="6800,10657,11495"; a="55231656" X-IronPort-AV: E=Sophos;i="6.16,320,1744095600"; d="scan'208";a="55231656" Received: from orviesa007.jf.intel.com ([10.64.159.147]) by orvoesa110.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Jul 2025 23:14:39 -0700 X-CSE-ConnectionGUID: QjMd2QMOTIW9uNutYiZLDg== X-CSE-MsgGUID: tZgUpPdKQHO9i74VxV/2pg== X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="6.16,320,1744095600"; d="scan'208";a="158062418" Received: from xiaoyaol-hp-g830.ccr.corp.intel.com (HELO [10.124.247.1]) ([10.124.247.1]) by orviesa007-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 17 Jul 2025 23:14:23 -0700 Message-ID: <0f31ab50-e30a-40d5-96ae-ee54742d98f9@intel.com> Date: Fri, 18 Jul 2025 14:14:17 +0800 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: [PATCH v15 19/21] KVM: Introduce the KVM capability KVM_CAP_GMEM_MMAP 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: <20250717162731.446579-1-tabba@google.com> <20250717162731.446579-20-tabba@google.com> Content-Language: en-US From: Xiaoyao Li In-Reply-To: <20250717162731.446579-20-tabba@google.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: 64ABE80002 X-Stat-Signature: njaidpop1o53nmzmsrfnoo1cnpaw79ja X-HE-Tag: 1752819279-16978 X-HE-Meta: U2FsdGVkX1957wZCs2AvZP52SfP1Lqi6v5UKGsrz5mGQefPbMNWDm/nR6m3TUn/1jXuoozUIQDQGrucBxH7Ynmh30DDFx2gp8mSdCin8ofeTFUf1Lrlm0xIUQh5wr8HYUZQpq+LFCmtSxJ2WuXb24MD7hqFwLmJb6abRBj1YzATf82z9XBdKu4m2Ga3dVZzn70j5eXlt2Rnfc4uOURxCci0ldQmxvkdeuF4fU0Xb6+Nsu4eLJTVx8ZISw1eua6ZTBBCokh34GaR+XsURRcD03cHQP0rW1vMRLcTVgleS/VXlviAXLzMQLE8XoasXWBbj0X8YQxU47zc7ZEdHsikZI3s9Z3AF3PqDM8BppRNDQCOuGhGntOzvqMprx4tLd5wTAhD6n6NXymk+VAgI+avVfalDLqf5meYyafsnWEYNXZ2/N56r3htix+TsxqylS0pmZ4EA2c7orZoKKiiUTeitRxKvTxjOMHR45kMrcvcxeFyCyHlE3nSl/+PUyLcaIXK/gFAwIarmRjf5ORoVcysZZkOfjuEY5FdktlXgWtsLRlZQZl369LpcvH6q7dTs93QcQarckbzPB6PX/E7jdeoACoCCm+BjbUb1+zk/w/k2+9TkrzMvZYF6UALmQE40T20n4/iONcPh9b2j6l+WahbX8YSJvuPsXCWWECyL9jZqBUKgxaBYeyLrgJK12/HchY4FtoLw4duYbXkY59EVRIOZfRv0cwG3j5N5dRcg8CcIADnUW1HRnn/Zi2WkNagz8YHBGk1+mKK0iYlUR16OSwKgtGaB7h40QiSoZWhEljmMXzZUcxbT6xT3tPFmG6q/Z5uQd6UqAV4OWLxzSgbQqCKql07y6LjMkOyzoQ++5wVvrwH0nmZ7NBfx6JWuNBSei498HSyOQaDDvS5NevwKNb+YPjXuruCflLClEz0PtFv9FyRheqBUUBsqG2Znc/MEKQU9siphR9vpK7Mq/MUDcS8 y8yRhWj5 UU6c+NEjJo0q86HbfX1Rgkj4SQ485Aofc/iPrKs1fjCROZRIxZk/fDFI5mF5MTNWcwTP5eRUtEPrQjE/ANgvDoJW6S1BKWB5SHBxOGW7Jllmglr8BBZFLEZ5HiXqvcXhtoy7uvqYkUFTQAGv8O3t6q6W2CTh9WVZ8YlBd4KTcqd7ycOHV+N69bOdyzNgev1nKrsU9ToAas6JQ5n4SylsPezJKa2604c7SZF+05OR/PynmgDYq1IcHb2pxilCHHLaaP+350J+LGqVPso757j6SRUVRpDBNmaOzirY5pOHjncG1KDRN/yFPA1KhR0g/9ln1+85Sm4APK08S/VfAifB1Ebqy3zrjJBAYK7W/gqJvk3PSurXBegUm6QQWXyYJCmFNrgitJZ8cYXeasB26PP4GS41kH+mDh4MVlrm/ 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/18/2025 12:27 AM, Fuad Tabba wrote: > Introduce the new KVM capability KVM_CAP_GMEM_MMAP. This capability > signals to userspace that a KVM instance supports host userspace mapping > of guest_memfd-backed memory. > > The availability of this capability is determined per architecture, and > its enablement for a specific guest_memfd instance is controlled by the > GUEST_MEMFD_FLAG_MMAP flag at creation time. > > Update the KVM API documentation to detail the KVM_CAP_GMEM_MMAP > capability, the associated GUEST_MEMFD_FLAG_MMAP, and provide essential > information regarding support for mmap in guest_memfd. > > Reviewed-by: David Hildenbrand > Reviewed-by: Gavin Shan > Reviewed-by: Shivank Garg > Signed-off-by: Fuad Tabba Reviewed-by: Xiaoyao Li Though I have comments on some patches, the general functionality for x86 seems to be work. I plan to do a POC with QEMU to test non-coco VM with guest_memfd with mmap support as the memory backend.