mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Anisa Su <anisa.su887@gmail.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: Anisa Su <anisa.su887@gmail.com>,
	linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
	nvdimm@lists.linux.dev, Dan Williams <djbw@kernel.org>,
	Jonathan Cameron <jic23@kernel.org>,
	Davidlohr Bueso <dave@stgolabs.net>,
	Vishal Verma <vishal.l.verma@intel.com>,
	Ira Weiny <iweiny@kernel.org>,
	Alison Schofield <alison.schofield@intel.com>,
	John Groves <John@groves.net>, Gregory Price <gourry@gourry.net>,
	Ira Weiny <ira.weiny@intel.com>
Subject: Re: [PATCH v10 22/31] cxl + dax: Release dax_resources on DCD Release Capacity events
Date: Tue, 16 Jun 2026 01:52:24 -0700	[thread overview]
Message-ID: <ajEOyOF3MrHVgACd@AnisaLaptop.localdomain> (raw)
In-Reply-To: <e5bd578c-15dc-4b69-9cd2-2eb3c3aa516a@intel.com>

On Thu, May 28, 2026 at 04:53:43PM -0700, Dave Jiang wrote:
> 
> 
> On 5/23/26 2:43 AM, Anisa Su wrote:
> > Implement the release path that mirrors the add path: when the
> > device asks for capacity back, the dax layer tears down the
> > per-extent resources for the whole tag group atomically.
> > 
> > If any extent in the group is still mapped by a dev_dax, the release
> > is refused with -EBUSY and no state changes; the cxl side then leaves
> > the tag group intact and the device retries.
> > 
> > Also add a rollback to the add path: if any per-extent registration
> > fails midway through a group, undo the ones already added so a
> > partial group never leaks into the dax region.
> > 
> > Based on an original patch by Navneet Singh.
> > 
> > Signed-off-by: Ira Weiny <ira.weiny@intel.com>
> > Signed-off-by: Anisa Su <anisa.su@samsung.com>
> 
> Just a nit below
> 
> Reviewed-by: Dave Jiang <dave.jiang@intel.com>
> 
> 
> > 
> > ---
> > Changes:
> > [anisa: split out from the original "Surface dc_extents" commit;
> >  fills in the RELEASE half of the bridge, moves the cxl-side RELEASE
> >  notify into this commit, and adds the rollback path to ADD.]
> > ---
> >  drivers/cxl/core/extent.c | 13 +++++++++
> >  drivers/dax/bus.c         | 59 +++++++++++++++++++++++++++++++++++++++
> >  drivers/dax/cxl.c         | 54 +++++++++++++++++++++++++++--------
> >  drivers/dax/dax-private.h |  8 ++++--
> >  4 files changed, 120 insertions(+), 14 deletions(-)
> > 
> > diff --git a/drivers/cxl/core/extent.c b/drivers/cxl/core/extent.c
> > index 3fc4b7292664..2c8edfe53c0a 100644
> > --- a/drivers/cxl/core/extent.c
> > +++ b/drivers/cxl/core/extent.c
> > @@ -532,6 +532,7 @@ int cxl_rm_extent(struct cxl_memdev_state *mds, struct cxl_extent *extent)
> >  	struct range dpa_range;
> >  	unsigned long idx;
> >  	uuid_t tag;
> > +	int rc;
> >  
> >  	dpa_range = (struct range) {
> >  		.start = start_dpa,
> > @@ -588,6 +589,18 @@ int cxl_rm_extent(struct cxl_memdev_state *mds, struct cxl_extent *extent)
> >  		return -EINVAL;
> >  	}
> >  
> > +	rc = cxlr_notify_extent(cxlr, DCD_RELEASE_CAPACITY, group);
> > +	if (rc) {
> > +		/*
> > +		 * dax layer refused (-EBUSY) or failed (-ENOMEM, etc.).  Do
> > +		 * not proceed to tear down the tag group — leave its
> > +		 * dax_resources alive so we do not free them out from under
> > +		 * live dev_dax ranges.  The device will retry the release.
> > +		 */
> > +		return 0;
> > +	}
> > +
> > +	/* Release the entire tag group */
> >  	rm_tag_group(group);
> >  	return 0;
> >  }
> > diff --git a/drivers/dax/bus.c b/drivers/dax/bus.c
> > index a6ee59f2d8a1..6368bdfdf93a 100644
> > --- a/drivers/dax/bus.c
> > +++ b/drivers/dax/bus.c
> > @@ -253,6 +253,65 @@ int dax_region_add_resource(struct dax_region *dax_region,
> >  }
> >  EXPORT_SYMBOL_GPL(dax_region_add_resource);
> >  
> > +int dax_region_rm_resource(struct dax_region *dax_region,
> > +			   struct device *dev)
> > +{
> > +	struct dax_resource *dax_resource;
> > +
> > +	guard(rwsem_write)(&dax_region_rwsem);
> > +
> > +	dax_resource = dev_get_drvdata(dev);
> > +	if (!dax_resource)
> > +		return 0;
> > +
> > +	if (dax_resource->use_cnt)
> > +		return -EBUSY;
> > +
> > +	/*
> > +	 * release the resource under dax_region_rwsem to avoid races with
> > +	 * users trying to use the extent
> > +	 */
> > +	__dax_release_resource(dax_resource);
> > +	dev_set_drvdata(dev, NULL);
> > +	return 0;
> > +}
> > +EXPORT_SYMBOL_GPL(dax_region_rm_resource);
> 
> No reason to export. Seems only used within DAX.
> 
Called from static int cxl_dax_group_add() in drivers/dax/cxl.c so needs
to be exported from dax to dax_cxl I think?

> DJ
> 
Thanks,
Anisa
> > +
> > +/**
> > + * dax_region_rm_resources - atomically remove a set of dax_resources.
> > + *
> > + * Walk @devs twice under dax_region_rwsem.  First pass refuses the
> > + * operation if any member's use_cnt is non-zero; second pass releases
> > + * each.  This gives refuse-all-or-none semantics across the set, which
> > + * a tag group's atomic release relies on.  Devices with no
> > + * dax_resource attached are silently skipped.
> > + */
> > +int dax_region_rm_resources(struct dax_region *dax_region,
> > +			    struct device * const *devs, unsigned int n)
> > +{
> > +	unsigned int i;
> > +
> > +	guard(rwsem_write)(&dax_region_rwsem);
> > +
> > +	for (i = 0; i < n; i++) {
> > +		struct dax_resource *r = dev_get_drvdata(devs[i]);
> > +
> > +		if (r && r->use_cnt)
> > +			return -EBUSY;
> > +	}
> > +
> > +	for (i = 0; i < n; i++) {
> > +		struct dax_resource *r = dev_get_drvdata(devs[i]);
> > +
> > +		if (!r)
> > +			continue;
> > +		__dax_release_resource(r);
> > +		dev_set_drvdata(devs[i], NULL);
> > +	}
> > +	return 0;
> > +}
> > +EXPORT_SYMBOL_GPL(dax_region_rm_resources);
> > +
> >  bool static_dev_dax(struct dev_dax *dev_dax)
> >  {
> >  	return is_static(dev_dax->region);
> > diff --git a/drivers/dax/cxl.c b/drivers/dax/cxl.c
> > index 690cf625e052..04b73315a8f2 100644
> > --- a/drivers/dax/cxl.c
> > +++ b/drivers/dax/cxl.c
> > @@ -44,19 +44,52 @@ static int cxl_dax_group_add(struct dax_region *dax_region,
> >  
> >  	xa_for_each(&group->dc_extents, index, dc_extent) {
> >  		rc = __cxl_dax_add_resource(dax_region, dc_extent);
> > -		if (rc)
> > +		if (rc) {
> > +			/*
> > +			 * Unwind every dax_resource already added for this
> > +			 * group; one rm per owner suffices.
> > +			 */
> > +			struct dc_extent *u;
> > +			unsigned long uidx;
> > +
> > +			xa_for_each(&group->dc_extents, uidx, u) {
> > +				if (u == dc_extent)
> > +					break;
> > +				dax_region_rm_resource(dax_region, &u->dev);
> > +			}
> >  			return rc;
> > +		}
> >  	}
> >  	return 0;
> >  }
> >  
> > -/*
> > - * RELEASE is still a stub here — the atomic dax_region_rm_resources API
> > - * and its wire-up land in the next commit.  An incoming RELEASE returns
> > - * success and the cxl side proceeds to rm_tag_group(), which device-
> > - * unregisters each dc_extent; the devm action armed by
> > - * dax_region_add_resource() then tears down each dax_resource.
> > - */
> > +static int cxl_dax_group_rm(struct dax_region *dax_region,
> > +			    struct cxl_dc_tag_group *group)
> > +{
> > +	struct dc_extent *dc_extent;
> > +	struct device **devs;
> > +	unsigned long index;
> > +	unsigned int n = 0;
> > +	int rc;
> > +
> > +	if (!group->nr_extents)
> > +		return 0;
> > +
> > +	devs = kmalloc_array(group->nr_extents, sizeof(*devs), GFP_KERNEL);
> > +	if (!devs)
> > +		return -ENOMEM;
> > +
> > +	xa_for_each(&group->dc_extents, index, dc_extent) {
> > +		if (n == group->nr_extents)
> > +			break;
> > +		devs[n++] = &dc_extent->dev;
> > +	}
> > +
> > +	rc = dax_region_rm_resources(dax_region, devs, n);
> > +	kfree(devs);
> > +	return rc;
> > +}
> > +
> >  static int cxl_dax_region_notify(struct device *dev,
> >  				 struct cxl_notify_data *notify_data)
> >  {
> > @@ -68,10 +101,7 @@ static int cxl_dax_region_notify(struct device *dev,
> >  	case DCD_ADD_CAPACITY:
> >  		return cxl_dax_group_add(dax_region, group);
> >  	case DCD_RELEASE_CAPACITY:
> > -		dev_dbg(&cxlr_dax->dev,
> > -			"DCD RELEASE notify (tag %pUb): no-op (stub)\n",
> > -			&group->uuid);
> > -		return 0;
> > +		return cxl_dax_group_rm(dax_region, group);
> >  	case DCD_FORCED_CAPACITY_RELEASE:
> >  	default:
> >  		dev_err(&cxlr_dax->dev, "Unknown DC event %d\n",
> > diff --git a/drivers/dax/dax-private.h b/drivers/dax/dax-private.h
> > index f2ae5918f94d..414813a6137f 100644
> > --- a/drivers/dax/dax-private.h
> > +++ b/drivers/dax/dax-private.h
> > @@ -146,13 +146,17 @@ struct dax_resource {
> >  };
> >  
> >  /*
> > - * Similar to run_dax() dax_region_add_resource() is exported but is not
> > - * intended to be a generic operation outside the dax subsystem.  It is only
> > + * Similar to run_dax() dax_region_{add,rm}_resource() are exported but are not
> > + * intended to be generic operations outside the dax subsystem.  They are only
> >   * generic between the dax layer and the dax drivers.
> >   */
> >  int dax_region_add_resource(struct dax_region *dax_region, struct device *dev,
> >  			    resource_size_t start, resource_size_t length,
> >  			    const uuid_t *tag, u16 seq_num);
> > +int dax_region_rm_resource(struct dax_region *dax_region,
> > +			   struct device *dev);
> > +int dax_region_rm_resources(struct dax_region *dax_region,
> > +			    struct device * const *devs, unsigned int n);
> >  
> >  static inline struct dev_dax *to_dev_dax(struct device *dev)
> >  {
> 

  reply	other threads:[~2026-06-16  8:52 UTC|newest]

Thread overview: 95+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-23  9:42 [PATCH v10 00/31] DCD: Add support for Dynamic Capacity Devices (DCD) Anisa Su
2026-05-23  9:42 ` [PATCH v10 01/31] cxl/mbox: Flag " Anisa Su
2026-05-27 21:34   ` Dave Jiang
2026-05-30  6:22     ` Anisa Su
2026-05-23  9:42 ` [PATCH v10 02/31] cxl/mem: Read dynamic capacity configuration from the device Anisa Su
2026-05-27 22:28   ` Dave Jiang
2026-05-30  6:40     ` Anisa Su
2026-06-01 15:23       ` Dave Jiang
2026-06-02  9:46         ` Anisa Su
2026-05-23  9:42 ` [PATCH v10 03/31] cxl/cdat: Gather DSMAS data for DCD partitions Anisa Su
2026-05-27 23:16   ` Dave Jiang
2026-05-30  6:45     ` Anisa Su
2026-05-23  9:42 ` [PATCH v10 04/31] cxl/core: Enforce partition order/simplify partition calls Anisa Su
2026-05-27 23:37   ` Dave Jiang
2026-05-30  6:57     ` Anisa Su
2026-05-23  9:42 ` [PATCH v10 05/31] cxl/mem: Expose dynamic ram A partition in sysfs Anisa Su
2026-05-27 23:54   ` Dave Jiang
2026-05-27 23:56   ` Dave Jiang
2026-05-30  7:04     ` Anisa Su
2026-05-23  9:43 ` [PATCH v10 06/31] cxl/port: Add 'dynamic_ram_a' to endpoint decoder mode Anisa Su
2026-05-28  0:01   ` Dave Jiang
2026-05-30  7:07     ` Anisa Su
2026-05-23  9:43 ` [PATCH v10 07/31] cxl/region: Add DC DAX region support Anisa Su
2026-05-28  0:16   ` Dave Jiang
2026-06-02  9:22     ` Anisa Su
2026-06-02 15:42       ` Dave Jiang
2026-06-18 20:21   ` Alison Schofield
2026-05-23  9:43 ` [PATCH v10 08/31] cxl/events: Split event msgnum configuration from irq setup Anisa Su
2026-05-23  9:43 ` [PATCH v10 09/31] cxl/pci: Factor out interrupt policy check Anisa Su
2026-05-23  9:43 ` [PATCH v10 10/31] cxl/mem: Configure dynamic capacity interrupts Anisa Su
2026-05-28 16:21   ` Dave Jiang
2026-06-08  8:16     ` Anisa Su
2026-06-10 16:57       ` Dave Jiang
2026-06-11 18:19         ` Anisa Su
2026-05-23  9:43 ` [PATCH v10 11/31] cxl/core: Return endpoint decoder information from region search Anisa Su
2026-05-23  9:43 ` [PATCH v10 12/31] cxl/mem: Set up framework for handling DC Events Anisa Su
2026-05-28 16:40   ` Dave Jiang
2026-06-09 17:34     ` Anisa Su
2026-05-23  9:43 ` [PATCH v10 13/31] cxl/mem: Add 20 second timeout for stalled DC_ADD_CAPACITY chains Anisa Su
2026-05-28 16:57   ` Dave Jiang
2026-06-09 17:36     ` Anisa Su
2026-05-23  9:43 ` [PATCH v10 14/31] cxl/extent: Handle DC Add Capacity events Anisa Su
2026-05-28 19:06   ` Dave Jiang
2026-06-10  3:48     ` Anisa Su
2026-06-24  9:16   ` Anisa Su
2026-05-23  9:43 ` [PATCH v10 15/31] cxl/mem: Drop misaligned DCD extent groups Anisa Su
2026-05-28 21:03   ` Dave Jiang
2026-06-11  6:22     ` Anisa Su
2026-05-23  9:43 ` [PATCH v10 16/31] cxl/extent: Validate DC extent partition Anisa Su
2026-05-28 21:34   ` Dave Jiang
2026-06-11  7:35     ` Anisa Su
2026-06-24  9:04   ` Anisa Su
2026-05-23  9:43 ` [PATCH v10 17/31] cxl/mem: Enforce tag-group semantics Anisa Su
2026-05-23  9:43 ` [PATCH v10 18/31] cxl/extent: Handle DC Release Capacity events Anisa Su
2026-05-28 22:13   ` Dave Jiang
2026-06-12  5:56     ` Anisa Su
2026-05-23  9:43 ` [PATCH v10 19/31] cxl/extent: Enforce cross-region tag uniqueness Anisa Su
2026-05-28 22:44   ` Dave Jiang
2026-05-23  9:43 ` [PATCH v10 20/31] cxl/region/extent: Expose dc_extent information in sysfs Anisa Su
2026-05-28 22:54   ` Dave Jiang
2026-06-12  5:58     ` Anisa Su
2026-05-23  9:43 ` [PATCH v10 21/31] cxl + dax: Surface dax_resources on DCD Add Capacity events Anisa Su
2026-05-28 23:41   ` Dave Jiang
2026-06-16  8:44     ` Anisa Su
2026-05-23  9:43 ` [PATCH v10 22/31] cxl + dax: Release dax_resources on DCD Release " Anisa Su
2026-05-28 23:53   ` Dave Jiang
2026-06-16  8:52     ` Anisa Su [this message]
2026-05-23  9:43 ` [PATCH v10 23/31] dax/bus: Factor out dev dax resize logic Anisa Su
2026-06-24  8:36   ` Anisa Su
2026-05-23  9:43 ` [PATCH v10 24/31] dax/bus: Add uuid sysfs attribute to dax devices Anisa Su
2026-05-29 17:07   ` Dave Jiang
2026-05-23  9:43 ` [PATCH v10 25/31] dax/bus: Reject resize on DC dax devices and enforce 0-size creation Anisa Su
2026-05-29 17:16   ` Dave Jiang
2026-06-16  8:54     ` Anisa Su
2026-05-23  9:43 ` [PATCH v10 26/31] dax/bus: Tag-aware uuid claim and show on DC dax devices Anisa Su
2026-05-29 17:53   ` Dave Jiang
2026-06-16  9:01     ` Anisa Su
2026-05-23  9:43 ` [PATCH v10 27/31] cxl/region: Read existing extents on region creation Anisa Su
2026-05-29 21:30   ` Dave Jiang
2026-06-16  9:39     ` Anisa Su
2026-05-23  9:43 ` [PATCH v10 28/31] cxl/mem: Trace Dynamic capacity Event Record Anisa Su
2026-05-29 22:41   ` Dave Jiang
2026-06-16  9:59     ` Anisa Su
2026-05-23  9:43 ` [PATCH v10 29/31] tools/testing/cxl: Make event logs dynamic Anisa Su
2026-05-29 22:58   ` Dave Jiang
2026-06-16 10:29     ` Anisa Su
2026-05-23  9:43 ` [PATCH v10 30/31] tools/testing/cxl: Add DC Regions to mock mem data Anisa Su
2026-05-29 23:42   ` Dave Jiang
2026-06-25 11:22     ` Anisa Su
2026-05-23  9:43 ` [PATCH v10 31/31] Documentation/cxl: Document DCD extent handling and DC-backed DAX regions Anisa Su
2026-05-27 18:51 ` [PATCH v10 00/31] DCD: Add support for Dynamic Capacity Devices (DCD) Dave Jiang
2026-05-30  0:16   ` Anisa Su
2026-06-05  5:35 ` Alison Schofield
2026-06-08  7:54   ` Anisa Su
2026-06-24  7:49 ` Anisa Su

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=ajEOyOF3MrHVgACd@AnisaLaptop.localdomain \
    --to=anisa.su887@gmail.com \
    --cc=John@groves.net \
    --cc=alison.schofield@intel.com \
    --cc=dave.jiang@intel.com \
    --cc=dave@stgolabs.net \
    --cc=djbw@kernel.org \
    --cc=gourry@gourry.net \
    --cc=ira.weiny@intel.com \
    --cc=iweiny@kernel.org \
    --cc=jic23@kernel.org \
    --cc=linux-cxl@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nvdimm@lists.linux.dev \
    --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

all inboxes | Powered by JetHome®