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 DCA6FC433F5 for ; Tue, 15 Mar 2022 06:31:42 +0000 (UTC) Received: by kanga.kvack.org (Postfix) id 0720F8D0002; Tue, 15 Mar 2022 02:31:42 -0400 (EDT) Received: by kanga.kvack.org (Postfix, from userid 40) id F3D9A8D0001; Tue, 15 Mar 2022 02:31:41 -0400 (EDT) X-Delivered-To: int-list-linux-mm@kvack.org Received: by kanga.kvack.org (Postfix, from userid 63042) id DDDFB8D0002; Tue, 15 Mar 2022 02:31:41 -0400 (EDT) X-Delivered-To: linux-mm@kvack.org Received: from relay.hostedemail.com (relay.a.hostedemail.com [64.99.140.24]) by kanga.kvack.org (Postfix) with ESMTP id C8FED8D0001 for ; Tue, 15 Mar 2022 02:31:41 -0400 (EDT) Received: from smtpin02.hostedemail.com (a10.router.float.18 [10.200.18.1]) by unirelay01.hostedemail.com (Postfix) with ESMTP id A403F60F80 for ; Tue, 15 Mar 2022 06:31:41 +0000 (UTC) X-FDA: 79245649602.02.6576F6B Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by imf21.hostedemail.com (Postfix) with ESMTP id 94A0A1C0006 for ; Tue, 15 Mar 2022 06:31:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1647325900; x=1678861900; h=from:to:cc:subject:references:date:in-reply-to: message-id:mime-version; bh=T43rbjuUfmYFNJl+eyDeXU+oKMJm8uoX+WBhgwCcupw=; b=Lkznpc3BJiH8Masp/oMiGpi71kl+QrHHIBY6ANDWZMkuprr40AwGlbxW Gp0c5OpZkWuvux2Zyzs4VfgR30suYm/TotLg1xxL6GDf2jXOYS8kkAVw8 t5ghmP56l/5VVxaqVE+Gpx9x+1NbbsKV/86l1zZ0UpWU+KwRY/yeKDOox VnXOn0kYcicj81WeCKF31gVRi05YjIauS+cUzu3JhEBoztGAR6WJaPkQS aKbu46/FhBV5Z2bsvedGWXf3VZkuIc9NxE97BCSdIjdIXiJehoJ17w77+ 9HIW/XaFTOXKwfy5KBXBRqIBdaoOMZnT582bYFYP+dBDYLivBjp4/Pi16 Q==; X-IronPort-AV: E=McAfee;i="6200,9189,10286"; a="255953543" X-IronPort-AV: E=Sophos;i="5.90,182,1643702400"; d="scan'208";a="255953543" Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga102.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Mar 2022 23:31:38 -0700 X-IronPort-AV: E=Sophos;i="5.90,182,1643702400"; d="scan'208";a="515743481" Received: from yhuang6-desk2.sh.intel.com (HELO yhuang6-desk2.ccr.corp.intel.com) ([10.239.13.94]) by orsmga006-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Mar 2022 23:31:36 -0700 From: "Huang, Ying" To: Oscar Salvador Cc: Dave Hansen , Andrew Morton , Dave Hansen , Abhishek Goel , Baolin Wang , linux-mm@kvack.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH v2] mm: Only re-generate demotion targets when a numa node changes its N_CPU state References: <20220310120749.23077-1-osalvador@suse.de> <87mthxb514.fsf@yhuang6-desk2.ccr.corp.intel.com> <87czip73b4.fsf@yhuang6-desk2.ccr.corp.intel.com> <6b63d2ad-9b21-3fd6-37b4-31d7ad804c30@intel.com> Date: Tue, 15 Mar 2022 14:31:34 +0800 In-Reply-To: (Oscar Salvador's message of "Tue, 15 Mar 2022 07:13:37 +0100") Message-ID: <87tubz3ewp.fsf@yhuang6-desk2.ccr.corp.intel.com> User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) MIME-Version: 1.0 Content-Type: text/plain; charset=ascii X-Stat-Signature: xyearfg54fpt4qbobn8acf5n6tabp6mr Authentication-Results: imf21.hostedemail.com; dkim=pass header.d=intel.com header.s=Intel header.b=Lkznpc3B; spf=none (imf21.hostedemail.com: domain of ying.huang@intel.com has no SPF policy when checking 134.134.136.24) smtp.mailfrom=ying.huang@intel.com; dmarc=pass (policy=none) header.from=intel.com X-Rspam-User: X-Rspamd-Server: rspam08 X-Rspamd-Queue-Id: 94A0A1C0006 X-HE-Tag: 1647325900-863807 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: Oscar Salvador writes: > On Mon, Mar 14, 2022 at 08:20:57AM -0700, Dave Hansen wrote: >> Qemu, for instance, has a "mem-path" argument. It's typically used for >> using hugetlbfs as guest memory. But, there's nothing stopping you from >> pointing it to a DAX device or a file on a DAX filesystem that's backed >> by pmem. > > Thanks Dave. > > But that is somehow different, is not it? > When you use pmem backed memory as a RAM for the guest, the guest is not > seeing that as PMEM, but just as a normal RAM, right? > IOW, the guest cannot use that memory for demotion, as we can use it in > the host when configured. > > I might be missing something, I am using this qemu cmdline: > > $QEMU -enable-kvm -machine pc -smp 4 -cpu host -monitor pty -m 5G \ > -object memory-backend-file,id=pc.ram,size=5G,mem-path=/mnt/pmem,share=off -machine memory-backend=pc.ram \ > $IMAGE -boot c -vnc :0 > > (/mnt/pmem was mounted with "mount -o dax /dev/pmem1 /mnt/pmem/") > > My point is, if it is really true that the guest cannot use that memory for > demotion, then we would still need CONFIG_MEMORY_HOTPLUG, as that is the > only way to expose PMEM to any system to be used as a demotion option > (via add_memory_driver_managed() through kmem driver). > > Or am I missing some qemu magic to use that memory as demotion in the > guest as well? You need to put PMEM to a NUMA node to use demotion, as follows, qemu-system-x86_64 --enable-kvm \ -M pc,accel=kvm,nvdimm=on -smp 8 -m 160G,slots=18,maxmem=703G \ -object memory-backend-ram,id=mem0,size=32G \ -object memory-backend-file,id=mem1,share=on,mem-path=/dev/dax0.0,size=128G,align=2M \ -numa node,memdev=mem0,cpus=0-7,nodeid=0 \ -numa node,memdev=mem1,nodeid=1 \ $IMAGE Best Regards, Huang, Ying