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 6E463C6370A for ; Thu, 8 Dec 2022 11:34:39 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id E679D8E0003; Thu, 8 Dec 2022 06:34:38 -0500 (EST) Received: by kanga.kvack.org (Postfix, from userid 40) id E171E8E0001; Thu, 8 Dec 2022 06:34:38 -0500 (EST) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id CDE708E0003; Thu, 8 Dec 2022 06:34:38 -0500 (EST) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (smtprelay0010.hostedemail.com [216.40.44.10]) by kanga.kvack.org (Postfix) with ESMTP id BE9408E0001 for ; Thu, 8 Dec 2022 06:34:38 -0500 (EST) Received: from smtpin18.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay01.hostedemail.com (Postfix) with ESMTP id 9583C1C2D12 for ; Thu, 8 Dec 2022 11:34:38 +0000 (UTC) X-FDA: 80218931436.18.70FB97B Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by imf29.hostedemail.com (Postfix) with ESMTP id F286D120003 for ; Thu, 8 Dec 2022 11:34:35 +0000 (UTC) Authentication-Results: imf29.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=WM7Gsh2b; spf=none (imf29.hostedemail.com: domain of chao.p.peng@linux.intel.com has no SPF policy when checking 192.55.52.120) smtp.mailfrom=chao.p.peng@linux.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=1670499276; h=from:from:sender:reply-to: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: in-reply-to:in-reply-to:references:references:dkim-signature; bh=qi/aamnMuLDAzihnFhxKn6t/hBuvRxKcYgOREsgdRcM=; b=Ig8SjFebDL8LDSesuRri2Adlq+JUBobCUZS/EJmCNowkiKKNwAjK3JFHIeg5mO2y8FDbjh S6Y4O+XjN083UM9LGCotUQYgt1IwOE7w6RWz5i5Lp69ILIJ3spGxI3CQ24x9752OhHP4fg pf2IF8BdNvgEv7j3CKXEYQEvq9Bwack= ARC-Authentication-Results: i=1; imf29.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=WM7Gsh2b; spf=none (imf29.hostedemail.com: domain of chao.p.peng@linux.intel.com has no SPF policy when checking 192.55.52.120) smtp.mailfrom=chao.p.peng@linux.intel.com; dmarc=pass (policy=none) header.from=intel.com ARC-Seal: i=1; s=arc-20220608; d=hostedemail.com; t=1670499276; a=rsa-sha256; cv=none; b=En3guF7WQitzmefWnr/P8cP3coakJlqmd3CCMOfszJQNZSMkPrRFRtqMR1OGFeJAbByp3t Cj/QOZYChSuhtnQjM7HMLkm+h3ap2dN01XCd7ymChV+tkJTbV2zlpfNDq0NgLye4+fNCrC 0jiBpCbK9qMGQOLPBTM/v9PQHZetkss= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1670499276; x=1702035276; h=date:from:to:cc:subject:message-id:reply-to:references: mime-version:in-reply-to; bh=BNKj0Q3HaLW0QQmlzFra5ewPCCLiShH0XE7KzON/axc=; b=WM7Gsh2bNAuT7e8b5qu/1wfdgzA3prTpL5laipFvvDq56BoNtWAjYO7l pFmHNZyco4UIkfy1yipwis6A14NvgwoRi4K/Kg6LyVLd7VwOmGrNRwar2 dABcvXrYmG+k3Gm5v+UKRAhXzBT/KwtuoYbRA8Gg66VPgrEb9Fy3Rpdlv RwBVnqL+Q7+6tLj3AZmMjf/dKL3En6tVf1n8ZmIj08xcZKcY08aGRxKwD cFjqnDFjV3RLSanNni0FRn+3umGkb11Sc+U3pwnD6Vf+rmiBeqH0YOU0d q275g+gXb/8js34iGInkmU11Ve51JlHsQB/2CXoy1qWo464VDcj3hC5XH g==; X-IronPort-AV: E=McAfee;i="6500,9779,10554"; a="315865235" X-IronPort-AV: E=Sophos;i="5.96,227,1665471600"; d="scan'208";a="315865235" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by fmsmga104.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 08 Dec 2022 03:34:34 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=McAfee;i="6500,9779,10554"; a="624670349" X-IronPort-AV: E=Sophos;i="5.96,227,1665471600"; d="scan'208";a="624670349" Received: from chaop.bj.intel.com (HELO localhost) ([10.240.193.75]) by orsmga006.jf.intel.com with ESMTP; 08 Dec 2022 03:34:22 -0800 Date: Thu, 8 Dec 2022 19:30:03 +0800 From: Chao Peng To: Xiaoyao Li 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 Subject: Re: [PATCH v10 3/9] KVM: Extend the memslot to support fd-based private memory Message-ID: <20221208113003.GE1304936@chaop.bj.intel.com> Reply-To: Chao Peng References: <20221202061347.1070246-1-chao.p.peng@linux.intel.com> <20221202061347.1070246-4-chao.p.peng@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: X-Rspamd-Server: rspam05 X-Rspamd-Queue-Id: F286D120003 X-Stat-Signature: qfkwe1mjhobr8fjr58nmbj3priqgy76o X-Rspam-User: X-HE-Tag: 1670499275-676531 X-HE-Meta: U2FsdGVkX18V2HCtPMsZnPUFWC9zM7SO3dU6L3N7kZBxSr4By0MScDQnWg5oPpHZ3E6YjxLN3UV+C6g1xSNf+KZ2P2zTUQQRUHiTmqtdKGceQA7lKWKaO5DyrAQ9ZRewOQXWJBK1tU+AFJS5hrEJgRu9HddONKShr1+TBSIG1otZXAosMH5PvCfW3lh8kwYnLqtfpazUJmql5j8S9rft1GrTR34+hsFqL27uIJar+A7MrUTbA1BkAaGvIXdUSR4qyMZ1nfmyu3Kq/nsAyZpLObRKVvyBax7FdL8dG6cuq1fbs0DkOLwsohuUPohOeeM0eaRwIUR+1Q89zX88OevogDbzYoMic6KIyoZP0clzYs8mJCCgCODQWefXOVYhI6Vf+vKcpKNkJnR773EjzYhWPo+xgUFI/dJaE2GyeduzT374upy7g1GVEw2c1mpeDGdnVHInLh2mmuuI4+x5S3oalP4BebpapcQqglVPXVXa5aP/Rsh3MgslfQyWnRfu4CLQ12HteWGjt7qK8km0JpdBy/ppNMSitreo7Op3j/8IlapZhzwGywOYwuryES1PRyZ4zhVlt5570eJ3crLjmr/MfurFnwRoCYnX3luJxnZQgumLeUYdumZO/h9zHlG+exuDuQ9qJDDUOYW2eSFvGAAHPr9J2Esq7tZw2Gszz809vLqZcmh6a/RntooZI0nS9k69+T7FLZ3oYAm3wwGsmB0Xdp6bwDtVxlJ6sXP1N8Z2wAhCHy6Dwzz84xDX3XB8rDr5ztjCJhvc2f/TU6fNxD/ys0pLY0veLL0n8jVkoZkA23No1V9mP9tArgLaqGk6BXqJ8OGCKPO18HcOnVIokIeVNRWWtAmYJhTSDVY/S+6Lb6HooIk9ycrTLtb7+z4Nez4vJg/vwB5syLnsIJML1RjHeP0kWcNTh9TIsubafqiq1GLsQoy2AKli+wsL8WmimujocvNFjQSsfbg= 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 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. Here is the original discussion: https://lore.kernel.org/all/YkJLFu98hZOvTSrL@google.com/ Thanks, Chao