Linux CXL
 help / color / mirror / Atom feed
From: "Verma, Vishal L" <vishal.l.verma@intel.com>
To: "john@jagalactic.com" <john@jagalactic.com>,
	"Williams, Dan J" <dan.j.williams@intel.com>
Cc: "johnny.li@montage-tech.com" <johnny.li@montage-tech.com>,
	"Widawsky, Ben" <ben.widawsky@intel.com>,
	"linux-cxl@vger.kernel.org" <linux-cxl@vger.kernel.org>,
	"Jonathan.Cameron@huawei.com" <Jonathan.Cameron@huawei.com>,
	"jgroves@micron.com" <jgroves@micron.com>
Subject: Re: CXL 1.1 Support Plan
Date: Thu, 7 Oct 2021 21:30:12 +0000	[thread overview]
Message-ID: <8a9b94becf407e218a544d3d0d9286ec4c698099.camel@intel.com> (raw)
In-Reply-To: <0100017c38c8cbb1-c0632347-44dd-44a4-b6c2-4e33c2ba85e8-000000@email.amazonses.com>

On Thu, 2021-09-30 at 22:17 +0000, John Groves wrote:
> > > 
> I don't see your doc patch yet in the ndctl repo, but I recommend merging it there.
> 
> A related question: "daxctl reconfigure-device --mode=system-ram ..." works for me,
> with --force, but going the other way (--mode=devdax) fails.  But a reboot puts it back
> into devdax mode regardless of the pre-boot setting (i.e. --mode=system-ram reverts
> back to devdax on reboot).

Oh, I'm a bit confused. --force only applies when going from system-ram
to devdax -- it offlines the memory for you. Without force, you're
responsible for a prior 'daxctl offline-memory daxX.Y' step.

Going from devdax to system-ram should not need --force, and I don't
think force actually does anything there.

> 
> Is reconfigure-device capable of remaining in effect after a reboot (in which case I'm curious
> how you persist the info if the device is volatile; I believe it's the LSA on a non-volatile
> device).

The beginnings of this automation are in progress, at least for
converting pmem devices:

  https://lore.kernel.org/nvdimm/20210831090459.2306727-1-vishal.l.verma@intel.com/

This is yet to be extended to volatile dax devices after figuring out
what property we can key off of - one idea is the 'target_node' from
ACPI.

> 
> Back to the patch: you mention --mode=system-ram, but it might be helpful to add
> a mention of --mode=devdax, along with a mention of whether (and how) these
> changes are persisted.

The rest of the man page talks a little bit about the modes:

  https://pmem.io/ndctl/daxctl-reconfigure-device.html

Dan - you haven't posted the patch you attached to the list yet have
you? /me couldn't find it on lore - wasn't sure if I'd just missed it.



  reply	other threads:[~2021-10-07 21:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-11  0:18 CXL 1.1 Support Plan johnny
2021-08-10 15:21 ` Dan Williams
2021-09-13 14:46   ` John Groves
2021-09-13 19:08     ` Dan Williams
2021-09-14 19:55       ` John Groves
2021-09-14 20:20         ` Dan Williams
2021-09-30 22:17           ` John Groves
     [not found]             ` <c55b69bd-45e3-4dec-91af-02ca4eeb054a@jagalactic.com>
2021-10-07 21:30             ` Verma, Vishal L [this message]
2021-10-08 18:06               ` John Groves
2021-10-08 18:10                 ` John Groves
2021-10-08 18:43               ` John Groves
2021-10-08 20:20                 ` Verma, Vishal L

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=8a9b94becf407e218a544d3d0d9286ec4c698099.camel@intel.com \
    --to=vishal.l.verma@intel.com \
    --cc=Jonathan.Cameron@huawei.com \
    --cc=ben.widawsky@intel.com \
    --cc=dan.j.williams@intel.com \
    --cc=jgroves@micron.com \
    --cc=john@jagalactic.com \
    --cc=johnny.li@montage-tech.com \
    --cc=linux-cxl@vger.kernel.org \
    /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