From: Dave Jiang <dave.jiang@intel.com>
To: Gregory Price <gourry@gourry.net>, linux-mm@kvack.org
Cc: nvdimm@lists.linux.dev, linux-kernel@vger.kernel.org,
linux-cxl@vger.kernel.org, driver-core@lists.linux.dev,
linux-kselftest@vger.kernel.org, kernel-team@meta.com,
david@kernel.org, osalvador@suse.de, gregkh@linuxfoundation.org,
rafael@kernel.org, dakr@kernel.org, djbw@kernel.org,
vishal.l.verma@intel.com, alison.schofield@intel.com,
akpm@linux-foundation.org, ljs@kernel.org, liam@infradead.org,
vbabka@kernel.org, rppt@kernel.org, surenb@google.com,
mhocko@suse.com, shuah@kernel.org, iweiny@kernel.org,
Smita.KoralahalliChannabasappa@amd.com, apopple@nvidia.com
Subject: Re: [PATCH v6 08/10] dax/kmem: extract hotplug/hotremove helper functions
Date: Thu, 9 Jul 2026 14:44:25 -0700 [thread overview]
Message-ID: <151783f1-c0e4-4c2b-a051-1e6e9c546cae@intel.com> (raw)
In-Reply-To: <20260630211842.2252800-9-gourry@gourry.net>
On 6/30/26 2:18 PM, Gregory Price wrote:
> Refactor kmem _probe() _remove() by extracting init, cleanup, hotplug,
> and hot-remove logic into separate helper functions:
>
> - dax_kmem_init_resources: inits IO_RESOURCE w/ request_mem_region
> - dax_kmem_cleanup_resources: cleans up initialized IO_RESOURCE
> - dax_kmem_do_hotplug: handles memory region reservation and adding
> - dax_kmem_do_hotremove: handles memory removal and resource cleanup
>
> This is a pure refactoring with no functional change. The helpers will
> enable future extensions to support more granular control over memory
> hotplug operations.
>
> We need to split hotplug/hotunplug and init/cleanup in order to have the
> resources available for hot-add. Otherwise, when probe occurs, the dax
> devices are never added to sysfs because the resources are never
> registered.
>
> Detatching hotunplug/cleanup allows us to re-use the hotunplug code
> without destroying the underlying resources.
>
> Signed-off-by: Gregory Price <gourry@gourry.net>
Minor comment below
Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> ---
> drivers/dax/kmem.c | 327 +++++++++++++++++++++++++++++++--------------
> 1 file changed, 225 insertions(+), 102 deletions(-)
>
> diff --git a/drivers/dax/kmem.c b/drivers/dax/kmem.c
> index 0a184c0878dd..72dcccee41e1 100644
> --- a/drivers/dax/kmem.c
> +++ b/drivers/dax/kmem.c
> @@ -63,14 +63,206 @@ static void kmem_put_memory_types(void)
> mt_put_memory_types(&kmem_memory_types);
> }
>
> +/**
> + * dax_kmem_do_hotplug - hotplug memory for dax kmem device
> + * @dev_dax: the dev_dax instance
> + * @data: the dax_kmem_data structure with resource tracking
> + *
> + * Hotplugs all ranges in the dev_dax region as system memory.
> + *
> + * Returns the number of successfully mapped ranges, or negative error.
> + */
> +static int dax_kmem_do_hotplug(struct dev_dax *dev_dax,
> + struct dax_kmem_data *data,
> + int online_type)
> +{
> + struct device *dev = &dev_dax->dev;
> + int i, rc, onlined = 0;
> + mhp_t mhp_flags;
> +
> + for (i = 0; i < dev_dax->nr_range; i++) {
> + struct range range;
> +
> + rc = dax_kmem_range(dev_dax, i, &range);
> + if (rc)
> + continue;
> +
> + /*
> + * init_resources() is best-effort: if a reservation conflict
> + * occurs it keeps the range but leaves res[i]=NULL. For hotplug
> + * on probe systems, this means kmem will partially online.
> + *
> + * We have to keep this behavior not to break those systems.
> + * For those systems - atomicity only applies to valid ranges.
> + */
> + if (!data->res[i])
> + continue;
> +
> + mhp_flags = MHP_NID_IS_MGID;
> + if (dev_dax->memmap_on_memory)
> + mhp_flags |= MHP_MEMMAP_ON_MEMORY;
> +
> + /*
> + * Ensure that future kexec'd kernels will not treat
> + * this as RAM automatically.
> + */
> + rc = __add_memory_driver_managed(data->mgid, range.start,
> + range_len(&range), kmem_name, mhp_flags,
> + online_type);
> +
> + if (rc) {
> + dev_warn(dev, "mapping%d: %#llx-%#llx memory add failed\n",
> + i, range.start, range.end);
> + /*
> + * Release the reservation for the range that failed to
> + * add so a later hotremove does not try to remove memory
> + * that was never added.
> + */
> + if (data->res[i]) {
> + remove_resource(data->res[i]);
> + kfree(data->res[i]);
> + data->res[i] = NULL;
> + }
> + if (onlined)
> + continue;
> + return rc;
> + }
> + onlined++;
> + }
> +
> + return onlined;
> +}
> +
> +/**
> + * dax_kmem_init_resources - create memory regions for dax kmem
> + * @dev_dax: the dev_dax instance
> + * @data: the dax_kmem_data structure with resource tracking
> + *
> + * Initializes all the resources for the DAX
> + *
> + * Returns the number of successfully mapped ranges, or negative error.
> + */
> +static int dax_kmem_init_resources(struct dev_dax *dev_dax,
> + struct dax_kmem_data *data)
> +{
> + struct device *dev = &dev_dax->dev;
> + int i, rc, mapped = 0;
> +
> + for (i = 0; i < dev_dax->nr_range; i++) {
> + struct resource *res;
> + struct range range;
> +
> + rc = dax_kmem_range(dev_dax, i, &range);
> + if (rc)
> + continue;
> +
> + /* Skip ranges already added */
> + if (data->res[i])
> + continue;
> +
> + /* Region is permanently reserved if hotremove fails. */
> + res = request_mem_region(range.start, range_len(&range),
> + data->res_name);
> + if (!res) {
> + dev_warn(dev, "mapping%d: %#llx-%#llx could not reserve region\n",
> + i, range.start, range.end);
> + /*
> + * Once some memory has been onlined we can't
> + * assume that it can be un-onlined safely.
> + */
> + if (mapped)
> + continue;
> + return -EBUSY;
> + }
> + data->res[i] = res;
> + /*
> + * Set flags appropriate for System RAM. Leave ..._BUSY clear
> + * so that add_memory() can add a child resource. Do not
> + * inherit flags from the parent since it may set new flags
> + * unknown to us that will break add_memory() below.
'later' instead of 'below'? Comment reflects previous function flow that is no longer the case.
DJ
> + */
> + res->flags = IORESOURCE_SYSTEM_RAM;
> + mapped++;
> + }
> + return mapped;
> +}
> +
> +#ifdef CONFIG_MEMORY_HOTREMOVE
> +/**
> + * dax_kmem_do_hotremove - hot-remove memory for dax kmem device
> + * @dev_dax: the dev_dax instance
> + * @data: the dax_kmem_data structure with resource tracking
> + *
> + * Removes all ranges in the dev_dax region.
> + *
> + * Returns the number of successfully removed ranges.
> + */
> +static int dax_kmem_do_hotremove(struct dev_dax *dev_dax,
> + struct dax_kmem_data *data)
> +{
> + struct device *dev = &dev_dax->dev;
> + int i, success = 0;
> +
> + for (i = 0; i < dev_dax->nr_range; i++) {
> + struct range range;
> + int rc;
> +
> + rc = dax_kmem_range(dev_dax, i, &range);
> + if (rc)
> + continue;
> +
> + /* range was never added during probe, count as removed */
> + if (!data->res[i]) {
> + success++;
> + continue;
> + }
> +
> + rc = remove_memory(range.start, range_len(&range));
> + if (rc == 0) {
> + /* Release the resource for the successfully removed range */
> + remove_resource(data->res[i]);
> + kfree(data->res[i]);
> + data->res[i] = NULL;
> + success++;
> + continue;
> + }
> + any_hotremove_failed = true;
> + dev_err(dev, "mapping%d: %#llx-%#llx hotremove failed\n",
> + i, range.start, range.end);
> + }
> +
> + return success;
> +}
> +#endif /* CONFIG_MEMORY_HOTREMOVE */
> +
> +/**
> + * dax_kmem_cleanup_resources - remove the dax memory resources
> + * @dev_dax: the dev_dax instance
> + * @data: the dax_kmem_data structure with resource tracking
> + *
> + * Removes all resources in the dev_dax region.
> + */
> +static void dax_kmem_cleanup_resources(struct dev_dax *dev_dax,
> + struct dax_kmem_data *data)
> +{
> + int i;
> +
> + for (i = 0; i < dev_dax->nr_range; i++) {
> + if (!data->res[i])
> + continue;
> + remove_resource(data->res[i]);
> + kfree(data->res[i]);
> + data->res[i] = NULL;
> + }
> +}
> +
> static int dev_dax_kmem_probe(struct dev_dax *dev_dax)
> {
> struct device *dev = &dev_dax->dev;
> unsigned long total_len = 0, orig_len = 0;
> struct dax_kmem_data *data;
> struct memory_dev_type *mtype;
> - int i, rc, mapped = 0;
> - mhp_t mhp_flags;
> + int i, rc;
> int numa_node;
> int online_type;
> int adist = MEMTIER_DEFAULT_DAX_ADISTANCE;
> @@ -133,73 +325,27 @@ static int dev_dax_kmem_probe(struct dev_dax *dev_dax)
> goto err_reg_mgid;
> data->mgid = rc;
>
> + dev_set_drvdata(dev, data);
> +
> + rc = dax_kmem_init_resources(dev_dax, data);
> + if (rc < 0)
> + goto err_resources;
> +
> /* Resolve system default at bind time in case it changed */
> online_type = dev_dax->online_type;
> if (online_type == DAX_ONLINE_DEFAULT)
> online_type = mhp_get_default_online_type();
>
> - for (i = 0; i < dev_dax->nr_range; i++) {
> - struct resource *res;
> - struct range range;
> -
> - rc = dax_kmem_range(dev_dax, i, &range);
> - if (rc)
> - continue;
> -
> - /* Region is permanently reserved if hotremove fails. */
> - res = request_mem_region(range.start, range_len(&range), data->res_name);
> - if (!res) {
> - dev_warn(dev, "mapping%d: %#llx-%#llx could not reserve region\n",
> - i, range.start, range.end);
> - /*
> - * Once some memory has been onlined we can't
> - * assume that it can be un-onlined safely.
> - */
> - if (mapped)
> - continue;
> - rc = -EBUSY;
> - goto err_request_mem;
> - }
> - data->res[i] = res;
> -
> - /*
> - * Set flags appropriate for System RAM. Leave ..._BUSY clear
> - * so that add_memory() can add a child resource. Do not
> - * inherit flags from the parent since it may set new flags
> - * unknown to us that will break add_memory() below.
> - */
> - res->flags = IORESOURCE_SYSTEM_RAM;
> -
> - mhp_flags = MHP_NID_IS_MGID;
> - if (dev_dax->memmap_on_memory)
> - mhp_flags |= MHP_MEMMAP_ON_MEMORY;
> -
> - /*
> - * Ensure that future kexec'd kernels will not treat
> - * this as RAM automatically.
> - */
> - rc = __add_memory_driver_managed(data->mgid, range.start,
> - range_len(&range), kmem_name, mhp_flags,
> - online_type);
> -
> - if (rc) {
> - dev_warn(dev, "mapping%d: %#llx-%#llx memory add failed\n",
> - i, range.start, range.end);
> - remove_resource(res);
> - kfree(res);
> - data->res[i] = NULL;
> - if (mapped)
> - continue;
> - goto err_request_mem;
> - }
> - mapped++;
> - }
> -
> - dev_set_drvdata(dev, data);
> + rc = dax_kmem_do_hotplug(dev_dax, data, online_type);
> + if (rc < 0)
> + goto err_hotplug;
>
> return 0;
>
> -err_request_mem:
> +err_hotplug:
> + dax_kmem_cleanup_resources(dev_dax, data);
> +err_resources:
> + dev_set_drvdata(dev, NULL);
> memory_group_unregister(data->mgid);
> err_reg_mgid:
> kfree(data->res_name);
> @@ -213,7 +359,7 @@ static int dev_dax_kmem_probe(struct dev_dax *dev_dax)
> #ifdef CONFIG_MEMORY_HOTREMOVE
> static void dev_dax_kmem_remove(struct dev_dax *dev_dax)
> {
> - int i, success = 0;
> + int success;
> int node = dev_dax->target_node;
> struct device *dev = &dev_dax->dev;
> struct dax_kmem_data *data = dev_get_drvdata(dev);
> @@ -224,48 +370,25 @@ static void dev_dax_kmem_remove(struct dev_dax *dev_dax)
> * there is no way to hotremove this memory until reboot because device
> * unbind will succeed even if we return failure.
> */
> - for (i = 0; i < dev_dax->nr_range; i++) {
> - struct range range;
> - int rc;
> -
> - rc = dax_kmem_range(dev_dax, i, &range);
> - if (rc)
> - continue;
> -
> - /* range was never added during probe */
> - if (!data->res[i]) {
> - success++;
> - continue;
> - }
> -
> - rc = remove_memory(range.start, range_len(&range));
> - if (rc == 0) {
> - remove_resource(data->res[i]);
> - kfree(data->res[i]);
> - data->res[i] = NULL;
> - success++;
> - continue;
> - }
> - any_hotremove_failed = true;
> - dev_err(dev,
> - "mapping%d: %#llx-%#llx cannot be hotremoved until the next reboot\n",
> - i, range.start, range.end);
> + success = dax_kmem_do_hotremove(dev_dax, data);
> + if (success < dev_dax->nr_range) {
> + dev_err(dev, "Hotplug regions stuck online until reboot\n");
> + return;
> }
>
> - if (success >= dev_dax->nr_range) {
> - memory_group_unregister(data->mgid);
> - kfree(data->res_name);
> - kfree(data);
> - dev_set_drvdata(dev, NULL);
> - /*
> - * Clear the memtype association on successful unplug.
> - * If not, we have memory blocks left which can be
> - * offlined/onlined later. We need to keep memory_dev_type
> - * for that. This implies this reference will be around
> - * till next reboot.
> - */
> - clear_node_memory_type(node, NULL);
> - }
> + dax_kmem_cleanup_resources(dev_dax, data);
> + memory_group_unregister(data->mgid);
> + kfree(data->res_name);
> + kfree(data);
> + dev_set_drvdata(dev, NULL);
> + /*
> + * Clear the memtype association on successful unplug.
> + * If not, we have memory blocks left which can be
> + * offlined/onlined later. We need to keep memory_dev_type
> + * for that. This implies this reference will be around
> + * till next reboot.
> + */
> + clear_node_memory_type(node, NULL);
> }
> #else
> static void dev_dax_kmem_remove(struct dev_dax *dev_dax)
next prev parent reply other threads:[~2026-07-09 21:44 UTC|newest]
Thread overview: 45+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-30 21:18 [PATCH v6 00/10] dax/kmem: atomic whole-device hotplug via sysfs Gregory Price
2026-06-30 21:18 ` [PATCH v6 01/10] mm/memory: add memory_block_aligned_range() helper Gregory Price
2026-07-09 17:58 ` Dave Jiang
2026-06-30 21:18 ` [PATCH v6 02/10] mm/memory_hotplug: add mhp_online_type_to_str() and export string helpers Gregory Price
2026-07-01 8:30 ` David Hildenbrand (Arm)
2026-07-09 17:59 ` Dave Jiang
2026-07-09 21:08 ` Dave Jiang
2026-07-09 21:57 ` Gregory Price
2026-07-10 12:44 ` David Hildenbrand (Arm)
2026-06-30 21:18 ` [PATCH v6 03/10] mm/memory_hotplug: pass online_type to online_memory_block() via arg Gregory Price
2026-07-09 18:22 ` Dave Jiang
2026-06-30 21:18 ` [PATCH v6 04/10] mm/memory_hotplug: export mhp_get_default_online_type Gregory Price
2026-07-09 18:30 ` Dave Jiang
2026-06-30 21:18 ` [PATCH v6 05/10] mm/memory_hotplug: add __add_memory_driver_managed() with online_type arg Gregory Price
2026-07-09 18:48 ` Dave Jiang
2026-06-30 21:18 ` [PATCH v6 06/10] mm/memory_hotplug: add offline_and_remove_memory_ranges() Gregory Price
2026-07-01 8:32 ` David Hildenbrand (Arm)
2026-07-09 8:45 ` Richard Cheng
2026-07-09 15:06 ` Gregory Price
2026-07-09 17:15 ` Gregory Price
2026-07-09 18:53 ` Dave Jiang
2026-06-30 21:18 ` [PATCH v6 07/10] dax: plumb hotplug online_type through dax Gregory Price
2026-07-09 21:07 ` Dave Jiang
2026-07-09 21:46 ` Dan Williams (nvidia)
2026-07-09 22:08 ` Gregory Price
2026-07-10 1:30 ` Gregory Price
2026-07-11 0:44 ` Dan Williams (nvidia)
2026-06-30 21:18 ` [PATCH v6 08/10] dax/kmem: extract hotplug/hotremove helper functions Gregory Price
2026-07-09 21:44 ` Dave Jiang [this message]
2026-07-09 21:57 ` Gregory Price
2026-06-30 21:18 ` [PATCH v6 09/10] dax/kmem: add sysfs interface for atomic whole-device hotplug Gregory Price
2026-06-30 22:14 ` Gregory Price
2026-07-01 6:13 ` Hannes Reinecke
2026-07-01 6:23 ` Gregory Price
2026-07-09 8:07 ` Richard Cheng
2026-07-09 14:57 ` Gregory Price
2026-07-09 22:14 ` Dave Jiang
2026-07-09 22:22 ` Gregory Price
2026-07-09 22:36 ` Dan Williams (nvidia)
2026-07-09 23:06 ` Gregory Price
2026-07-09 23:57 ` Dan Williams (nvidia)
2026-07-10 3:08 ` Gregory Price
2026-06-30 21:18 ` [PATCH v6 10/10] selftests/dax: add dax/kmem hotplug sysfs regression test Gregory Price
2026-07-09 8:20 ` Richard Cheng
2026-07-09 15:02 ` Gregory Price
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=151783f1-c0e4-4c2b-a051-1e6e9c546cae@intel.com \
--to=dave.jiang@intel.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=akpm@linux-foundation.org \
--cc=alison.schofield@intel.com \
--cc=apopple@nvidia.com \
--cc=dakr@kernel.org \
--cc=david@kernel.org \
--cc=djbw@kernel.org \
--cc=driver-core@lists.linux.dev \
--cc=gourry@gourry.net \
--cc=gregkh@linuxfoundation.org \
--cc=iweiny@kernel.org \
--cc=kernel-team@meta.com \
--cc=liam@infradead.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ljs@kernel.org \
--cc=mhocko@suse.com \
--cc=nvdimm@lists.linux.dev \
--cc=osalvador@suse.de \
--cc=rafael@kernel.org \
--cc=rppt@kernel.org \
--cc=shuah@kernel.org \
--cc=surenb@google.com \
--cc=vbabka@kernel.org \
--cc=vishal.l.verma@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