From: Dave Hansen <dave.hansen@intel.com>
To: Oscar Salvador <osalvador@suse.de>, "Huang, Ying" <ying.huang@intel.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Dave Hansen <dave.hansen@linux.intel.com>,
Abhishek Goel <huntbag@linux.vnet.ibm.com>,
Baolin Wang <baolin.wang@linux.alibaba.com>,
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
Date: Mon, 14 Mar 2022 08:20:57 -0700 [thread overview]
Message-ID: <6b63d2ad-9b21-3fd6-37b4-31d7ad804c30@intel.com> (raw)
In-Reply-To: <Yi9bhXSADpNt6WEC@localhost.localdomain>
On 3/14/22 08:13, Oscar Salvador wrote:
> On Mon, Mar 14, 2022 at 09:03:59AM +0800, Huang, Ying wrote:
>> Oscar Salvador <osalvador@suse.de> writes:
>> On host machine, PMEM is always exposed via memory hotplug. But later
>> on, we found that for guest system it's possible for PMEM to be exposed
>> as normal memory.
> Could you please elaborate on that? How is it done? I would love to hear the
> details.
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.
next prev parent reply other threads:[~2022-03-14 15:21 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-10 12:07 Oscar Salvador
2022-03-11 1:33 ` Baolin Wang
2022-03-11 2:24 ` Huang, Ying
2022-03-11 8:39 ` Oscar Salvador
2022-03-14 1:03 ` Huang, Ying
2022-03-14 15:13 ` Oscar Salvador
2022-03-14 15:20 ` Dave Hansen [this message]
2022-03-15 6:13 ` Oscar Salvador
2022-03-15 6:31 ` Huang, Ying
2022-03-11 2:39 ` Andrew Morton
2022-03-11 9:23 ` Oscar Salvador
2022-03-11 17:10 ` Dave Hansen
2022-03-14 9:09 ` Abhishek Goel
2022-03-11 5:06 ` Huang, Ying
2022-03-11 9:17 ` Oscar Salvador
2022-03-14 3:09 ` Huang, Ying
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=6b63d2ad-9b21-3fd6-37b4-31d7ad804c30@intel.com \
--to=dave.hansen@intel.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dave.hansen@linux.intel.com \
--cc=huntbag@linux.vnet.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=osalvador@suse.de \
--cc=ying.huang@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox