void release_mem_region_adjustable(resource_size_t start, resource_size_t size) { struct resource *parent = &iomem_resource; struct resource *new_res = NULL; bool alloc_nofail = false; struct resource **p; 2 changes: 1 addition & 1 deletion 2 mm/memory_hotplug.c Original file line nu...
release_mem_region(range.start, range_len(&range)); kfree(res_name); return rc; }dev_set_drvdata(dev, res_name); dev_dax->dax_kmem_res = new_res;return 0; } @@ -95,7 +92,6 @@ static int dev_dax_kmem_remove(struct device *dev) ...
devm_request_mem_region/devm_release_mem_region. These resources have the flag IORESOURCE_MEM, while resources acquired by hot-add memory path (register_memory_resource()) contain IORESOURCE_SYSTEM_RAM. So, we can check for this flag in release_mem_region_adjustable, and if the resource does ...
* devm_release_mem_region. * HMM/devm take care to release their resources when they want, * so if we are dealing with them, let us just back off here. */ if(!(res->flags&IORESOURCE_SYSRAM)) { ret=0; break; } if(!(res->flags&IORESOURCE_MEM)) ...