On Fri, 2019-10-18 at 13:46 -0700, Dan Williams wrote: > > > +'daxctl-reconfigure-device' nominally expects that it will online new > > memory > > +blocks as 'movable', so that kernel data doesn't make it into this memory. > > +However, there are other potential agents that may be configured to > > +automatically online new hot-plugged memory as it appears. Most notably, > > +these are the '/sys/devices/system/memory/auto_online_blocks' > > configuration, > > +or system udev rules. If such an agent races to online memory sections, > > daxctl > > +checks if the blocks were onlined as 'movable' memory. If this was not the > > +case, and the memory blocks are found to be in a different zone, then a > > +warning is displayed. If it is desired that a different agent control the > > +onlining of memory blocks, and the associated memory zone, then it is > > +recommended to use the --no-online option described below. This will > > abridge > > +the device reconfiguration operation to just hotplugging the memory, and > > +refrain from then onlining it. > > Oh here's that full description that calls out udev. > > I think just "See daxctl reconfigure-device --help" is sufficient for > those warnings in the previous patch.
Yep I've truncated the runtime warning down to point here. _______________________________________________ Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org To unsubscribe send an email to linux-nvdimm-le...@lists.01.org
