Add the "hotunplug" setting for NODE_PRIVATE_CAP_HOTUNPLUG, so the node's memory may be bulk-evacuated for device removal.
Signed-off-by: Gregory Price <[email protected]> --- drivers/dax/kmem.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/dax/kmem.c b/drivers/dax/kmem.c index 8023db23e2f99..3892ad44d4e46 100644 --- a/drivers/dax/kmem.c +++ b/drivers/dax/kmem.c @@ -630,11 +630,13 @@ static DEVICE_ATTR_RW(name) KMEM_PRIVATE_CAP_ATTR(reclaim, NODE_PRIVATE_CAP_RECLAIM); KMEM_PRIVATE_CAP_ATTR(user_numa, NODE_PRIVATE_CAP_USER_NUMA); +KMEM_PRIVATE_CAP_ATTR(hotunplug, NODE_PRIVATE_CAP_HOTUNPLUG); /* Per-service opt-ins. Visibility toggled by 'private' control */ static struct attribute *dax_kmem_private_attrs[] = { &dev_attr_reclaim.attr, &dev_attr_user_numa.attr, + &dev_attr_hotunplug.attr, NULL, }; static const struct attribute_group dax_kmem_private_group = { -- 2.53.0-Meta
