From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "Jiang, Dave" <dave.jiang@intel.com>,
"david@redhat.com" <david@redhat.com>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
"Huang, Ying" <ying.huang@intel.com>,
"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
"nvdimm@lists.linux.dev" <nvdimm@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Jonathan.Cameron@huawei.com" <Jonathan.Cameron@huawei.com>,
"dave.hansen@linux.intel.com" <dave.hansen@linux.intel.com>
Subject: Re: [PATCH v2 2/2] dax: add a sysfs knob to control memmap_on_memory behavior
Date: Fri, 8 Dec 2023 21:26:48 +0000 [thread overview]
Message-ID: <8bc94ef9834569f5b1e330ca7cde22b183d94444.camel@intel.com> (raw)
In-Reply-To: <e9323c58-6a99-436f-b8c5-ffc68b940de3@redhat.com>
On Fri, 2023-12-08 at 12:36 +0100, David Hildenbrand wrote:
> On 07.12.23 05:36, Vishal Verma wrote:
[..]
> >
> > +
> > +What: /sys/bus/dax/devices/daxX.Y/memmap_on_memory
> > +Date: October, 2023
> > +KernelVersion: v6.8
> > +Contact: nvdimm@lists.linux.dev
> > +Description:
> > + (RW) Control the memmap_on_memory setting if the dax device
> > + were to be hotplugged as system memory. This determines whether
> > + the 'altmap' for the hotplugged memory will be placed on the
> > + device being hotplugged (memmap_on+memory=1) or if it will be
> > + placed on regular memory (memmap_on_memory=0). This attribute
> > + must be set before the device is handed over to the 'kmem'
> > + driver (i.e. hotplugged into system-ram).
> >
>
> Should we note the dependency on other factors as given in
> mhp_supports_memmap_on_memory(), especially, the system-wide setting and
> some weird kernel configurations?
>
Yep good idea, I'll make a note of those for v3.
prev parent reply other threads:[~2023-12-08 21:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-07 4:36 [PATCH v2 0/2] Add DAX ABI for memmap_on_memory Vishal Verma
2023-12-07 4:36 ` [PATCH v2 1/2] Documentatiion/ABI: Add ABI documentation for sys-bus-dax Vishal Verma
2023-12-07 4:36 ` [PATCH v2 2/2] dax: add a sysfs knob to control memmap_on_memory behavior Vishal Verma
2023-12-07 8:29 ` Zhijian Li (Fujitsu)
2023-12-07 19:25 ` Verma, Vishal L
2023-12-08 9:20 ` Zhijian Li (Fujitsu)
2023-12-08 21:24 ` Verma, Vishal L
2023-12-08 3:13 ` Huang, Ying
2023-12-08 21:25 ` Verma, Vishal L
2023-12-08 11:36 ` David Hildenbrand
2023-12-08 21:26 ` Verma, Vishal L [this message]
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=8bc94ef9834569f5b1e330ca7cde22b183d94444.camel@intel.com \
--to=vishal.l.verma@intel.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=dan.j.williams@intel.com \
--cc=dave.hansen@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=david@redhat.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nvdimm@lists.linux.dev \
--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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).