From: Anisa Su <anisa.su887@gmail.com>
To: Richard Cheng <icheng@nvidia.com>
Cc: Anisa Su <anisa.su887@gmail.com>,
linux-cxl@vger.kernel.org, nvdimm@lists.linux.dev,
linux-kernel@vger.kernel.org, Dave Jiang <dave.jiang@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Jonathan Cameron <jic23@kernel.org>,
Davidlohr Bueso <dave@stgolabs.net>,
Ira Weiny <iweiny@kernel.org>,
Vishal Verma <vishal.l.verma@intel.com>,
Fan Ni <nifan.cxl@gmail.com>, Li Ming <ming.li@zohomail.com>,
Benjamin Cheatham <benjamin.cheatham@amd.com>,
Gregory Price <gourry@gourry.net>
Subject: Re: [PATCH v1 06/14] cxl/extent: Handle DC Add Capacity events
Date: Tue, 17 Nov 2026 06:53:41 +0900 [thread overview]
Message-ID: <avt7ZWXUvp9JrO80@cxlqual> (raw)
In-Reply-To: <avUsyj-2n-qB-ZIu@MWDK4CY14F>
On Thu, Nov 12, 2026 at 11:34:45AM +0800, Richard Cheng wrote:
> On Thu, Nov 05, 2026 at 08:02:30AM +0800, Anisa Su wrote:
> > From: Ira Weiny <iweiny@kernel.org>
> >
> > Replace the refuse-all stub for Add Capacity chains in
> > handle_dcd_chain_event() with the real add pipeline.
> >
> > DC Event Records can be grouped together with the 'More' flag. The
> > previous commit completed the set up for holding onto extents in
> > the pending list until receiving the last event record of the group,
> > marked by 'More'=0.
> >
> > This commit fills in the logic for processing the pending list and
> > adds basic validation for extents before they are added to the
> > device model as a child of the cxlr_dax region. More complete
> > checks for tags/sequence numbers/alignment are added in subsequent
> > commits.
> >
> > For each tag that appears in the pending list:
> > 1. Extract all extents in the pending list with that tag to a
> > local list.
> >
> > 2. The spec requires that shareable extents are ordered by
> > shared extent sequence number, which "instructs each host
> > on the relative order these extents must be placed in adjacent
> > virtual address space" (r4.0 Section 9.13.3 Figure 9-23
> > Shared Extent List Example). Otherwise, retain arrival order.
> >
> > Thus the tag group is stable-sorted by shared_extn_seq; for non-sharable
> > extents every key is 0 and the stable sort preserves arrival
> > order.
> >
> > Individual extents are checked for the following:
> > 1. The extent's DPA range fully resolves to an endpoint decoder.
> >
> > 2. Doesn't overlap or repeat a previously accepted extent; the device
> > rejects a DPA range reported twice in an Add response (r4.0 Section
> > 8.2.10.9.9.3, Invalid Physical Address).
> >
> > A tag group is one allocation, and for sharable capacity the host
> > must accept all of it or none (r4.0 Section 8.2.10.9.9.3, otherwise
> > the device returns Invalid Extent List). So an extent failing any of
> > these checks drops its whole group.
> >
> > Upon passing these checks, extents are "onlined" together as a
> > tag group:
> >
> > online_tag_group() registers a tagged group as a tag_groupX.Y device
> > under cxlr_dax->dev and a struct device per dc_extent under it.
> >
> > A single "untagged" device is registered under cxlr_dax when
> > accepting the first untagged extent. All future untagged extents
> > will be registered under it.
> >
> > A group that fails to online is dropped from the Add response.
> >
> > Once the pending list has been fully processed, send the
> > DC_ADD_RESPONSE.
> >
> > Region teardown invalidates the region's cached lines and releases all
> > extents under it.
> >
> > Based on an original patch by Navneet Singh.
> >
> > Signed-off-by: Ira Weiny <iweiny@kernel.org>
> > Co-developed-by: John Groves <John@Groves.net>
> > Signed-off-by: John Groves <John@Groves.net>
> > Co-developed-by: Anisa Su <anisa.su@samsung.com>
> > Signed-off-by: Anisa Su <anisa.su@samsung.com>
> > Tested-by: Wonjae Lee <wj28.lee@samsung.com>
> > Tested-by: Junhee Park <jh9934.park@samsung.com>
> > Tested-by: Heesoo Kim <habil.kim@samsung.com>
> > ---
> > drivers/cxl/core/Makefile | 2 +-
> > drivers/cxl/core/core.h | 33 +++
> > drivers/cxl/core/extent.c | 513 ++++++++++++++++++++++++++++++++++
> > drivers/cxl/core/mbox.c | 248 +++++++++++++++-
> > drivers/cxl/core/region.c | 2 +-
> > drivers/cxl/core/region_dax.c | 78 +++++-
> > drivers/cxl/cxl.h | 87 ++++++
> > drivers/cxl/cxlmem.h | 2 +
> > drivers/dax/bus.c | 13 +
> > tools/testing/cxl/Kbuild | 5 +-
> > 10 files changed, 974 insertions(+), 9 deletions(-)
> > create mode 100644 drivers/cxl/core/extent.c
> >
[snip]
> Hi Anisa, Ira,
>
> I'm thinking CXL/DAX should have a clearer boundary split.
>
> - CXL owns the device protocol, capacity acceptance, and recovery
> when the mailbox outcome is uncertain
> - DAX owns local resource management, all-or-none group insertion,
> and userspace claims.
>
>
> The interface should distinguish preparing resources from making them available.
> CXL can ask DAX to prepare a group before sending the Add Capacity Response,
> but those resources must remain unclaimable until CXL confirms acceptance
> with the device.
>
> CXL then tells DAX to make the group available. On a definite refusal,
> CXl requests cleanup. On an uncertain result, CXL keeps the group unavailable
> and reconciles the device state.
>
> The current ordering adds DAX resources before the Add Capacity Response
> completes. A successful dax_region_add_resources() only means that local
> insertion succeeded, it doesn't establish that the device accepted the
> allocation.
>
> That coordiation belongs in CXL. DAX should provide the resource
> operations and enforce availability according to CXL's decision.
>
> Best regards,
> Richard Cheng.
>
Hi Richard,
Thanks for the review. I agree with your point, but it seems simpler to
re-order the steps in cxl_add_pending() than to add a new "prepare" step.
So in cxl_add_pending(): validate and build tag groups, then send the
Add Response. If rc == 0, online the groups to DAX.
If onlining to DAX fails, then send a Release DC Response. If Release DC
response fails, maybe we can retry X number of times.
Does that keep the boundary between CXL/DAX you have in mind?
Also is it harder to review the series separately? While I was
splitting the series, I thought it may be difficult to make a very clean
split. Since you mentioned about onlining to DAX, which is not in this series,
I assume you looked at the DAX half.
Thanks,
Anisa
>
> > static int handle_dcd_chain_event(struct cxl_memdev_state *mds,
> > struct cxl_event_dcd *event)
> > {
> > @@ -1359,11 +1601,9 @@ static int handle_dcd_chain_event(struct cxl_memdev_state *mds,
> > chain->armed = false;
> > cancel_delayed_work(&chain->timeout_work);
> >
> > - /* Nothing is tracked yet: refuse every add, acknowledge every release */
> > if (event->event_type == DCD_ADD_CAPACITY)
> > - rc = cxl_send_dc_response(mds, CXL_MBOX_OP_ADD_DC_RESPONSE,
> > - &chain->pending_extents, 0);
> > - else
> > + rc = cxl_add_pending(mds, &chain->pending_extents);
> > + else /* Nothing is tracked yet: acknowledge every release */
> > rc = cxl_send_dc_response(mds, CXL_MBOX_OP_RELEASE_DC,
> > &chain->pending_extents,
> > list_count_nodes(&chain->pending_extents));
> > diff --git a/drivers/cxl/core/region.c b/drivers/cxl/core/region.c
> > index fc9139ce358f..1b7031b2f159 100644
> > --- a/drivers/cxl/core/region.c
> > +++ b/drivers/cxl/core/region.c
> > @@ -224,7 +224,7 @@ static struct cxl_region_ref *cxl_rr_load(struct cxl_port *port,
> > return xa_load(&port->regions, (unsigned long)cxlr);
> > }
> >
> > -static int cxl_region_invalidate_memregion(struct cxl_region *cxlr)
> > +int cxl_region_invalidate_memregion(struct cxl_region *cxlr)
> > {
> > if (!cpu_cache_has_invalidate_memregion()) {
> > if (IS_ENABLED(CONFIG_CXL_REGION_INVALIDATION_TEST)) {
> > diff --git a/drivers/cxl/core/region_dax.c b/drivers/cxl/core/region_dax.c
> > index 47c9c52a3902..790176a8aadd 100644
> > --- a/drivers/cxl/core/region_dax.c
> > +++ b/drivers/cxl/core/region_dax.c
> > @@ -13,6 +13,8 @@ static void cxl_dax_region_release(struct device *dev)
> > {
> > struct cxl_dax_region *cxlr_dax = to_cxl_dax_region(dev);
> >
> > + xa_destroy(&cxlr_dax->dc_extents);
> > + ida_destroy(&cxlr_dax->tag_group_ida);
> > kfree(cxlr_dax);
> > }
> >
> > @@ -27,6 +29,20 @@ const struct device_type cxl_dax_region_type = {
> > .groups = cxl_dax_region_attribute_groups,
> > };
> >
> > +static void cxl_dax_untagged_release(struct device *dev)
> > +{
> > + struct cxl_dax_region *cxlr_dax =
> > + container_of(dev, struct cxl_dax_region, untagged);
> > +
> > + /* Drop the pin taken in cxl_dax_region_alloc(). */
> > + put_device(&cxlr_dax->dev);
> > +}
> > +
> > +static const struct device_type cxl_dax_untagged_type = {
> > + .name = "untagged",
> > + .release = cxl_dax_untagged_release,
> > +};
> > +
> > static bool is_cxl_dax_region(struct device *dev)
> > {
> > return dev->type == &cxl_dax_region_type;
> > @@ -49,7 +65,8 @@ static struct cxl_dax_region *cxl_dax_region_alloc(struct cxl_region *cxlr)
> > struct cxl_dax_region *cxlr_dax;
> > struct device *dev;
> >
> > - guard(rwsem_read)(&cxl_rwsem.region);
> > + /* Publishes cxlr->cxlr_dax, which the event paths read under the read lock */
> > + guard(rwsem_write)(&cxl_rwsem.region);
> > if (p->state != CXL_CONFIG_COMMIT)
> > return ERR_PTR(-ENXIO);
> >
> > @@ -57,11 +74,14 @@ static struct cxl_dax_region *cxl_dax_region_alloc(struct cxl_region *cxlr)
> > if (!cxlr_dax)
> > return ERR_PTR(-ENOMEM);
> >
> > + xa_init_flags(&cxlr_dax->dc_extents, XA_FLAGS_ALLOC1);
> > + ida_init(&cxlr_dax->tag_group_ida);
> > cxlr_dax->hpa_range.start = p->res->start;
> > cxlr_dax->hpa_range.end = p->res->end;
> >
> > dev = &cxlr_dax->dev;
> > cxlr_dax->cxlr = cxlr;
> > + cxlr->cxlr_dax = cxlr_dax;
> > device_initialize(dev);
> > lockdep_set_class(&dev->mutex, &cxl_dax_region_key);
> > device_set_pm_not_required(dev);
> > @@ -69,16 +89,70 @@ static struct cxl_dax_region *cxl_dax_region_alloc(struct cxl_region *cxlr)
> > dev->bus = &cxl_bus_type;
> > dev->type = &cxl_dax_region_type;
> >
> > + /* Parent of the untagged extents, see cxl_dax_untagged_add() */
> > + dev = &cxlr_dax->untagged;
> > + device_initialize(dev);
> > + device_set_pm_not_required(dev);
> > + dev->parent = &cxlr_dax->dev;
> > + dev->type = &cxl_dax_untagged_type;
> > + get_device(&cxlr_dax->dev);
> > +
> > return cxlr_dax;
> > }
> >
> > +/*
> > + * Clearing cxlr->cxlr_dax here cannot race an Add or Release event.
> > + * Event paths find cxlr_dax through cxl_dpa_to_region() and use it with
> > + * cxl_rwsem.region held for read, from resolving an extent through
> > + * onlining its group. Taking the write lock waits those paths out, and
> > + * later lookups find NULL, so the teardown that follows sees no events.
> > + */
> > +static void cxlr_dax_unpublish(struct cxl_dax_region *cxlr_dax)
> > +{
> > + guard(rwsem_write)(&cxl_rwsem.region);
> > + cxlr_dax->cxlr->cxlr_dax = NULL;
> > +}
> > +
> > static void cxlr_dax_unregister(void *_cxlr_dax)
> > {
> > struct cxl_dax_region *cxlr_dax = _cxlr_dax;
> >
> > + cxlr_dax_unpublish(cxlr_dax);
> > + /* Unbind first: the driver's teardown empties untagged and the groups */
> > + device_release_driver(&cxlr_dax->dev);
> > + if (device_is_registered(&cxlr_dax->untagged))
> > + device_del(&cxlr_dax->untagged);
> > + put_device(&cxlr_dax->untagged);
> > device_unregister(&cxlr_dax->dev);
> > }
> >
> > +/*
> > + * The dax_region's driver may probe, and its extent scan run, before
> > + * devm_cxl_add_dax_region() returns, so the untagged device is registered
> > + * on first use instead. Callers are serialized by the memdev's
> > + * dc_chain.lock; a DC region has a single memdev behind it.
> > + */
> > +int cxl_dax_untagged_add(struct cxl_dax_region *cxlr_dax)
> > +{
> > + struct device *dev = &cxlr_dax->untagged;
> > + int rc;
> > +
> > + if (device_is_registered(dev))
> > + return 0;
> > +
> > + rc = dev_set_name(dev, "untagged");
> > + if (rc)
> > + return rc;
> > + return device_add(dev);
> > +}
> > +
> > +DEFINE_FREE(unpublish_cxl_dax_region, struct cxl_dax_region *,
> > + if (!IS_ERR_OR_NULL(_T)) {
> > + cxlr_dax_unpublish(_T);
> > + put_device(&_T->untagged);
> > + put_device(&_T->dev);
> > + })
> > +
> > int devm_cxl_add_dax_region(struct cxl_region *cxlr)
> > {
> > struct device *dev;
> > @@ -90,7 +164,7 @@ int devm_cxl_add_dax_region(struct cxl_region *cxlr)
> > return -EINVAL;
> > }
> >
> > - struct cxl_dax_region *cxlr_dax __free(put_cxl_dax_region) =
> > + struct cxl_dax_region *cxlr_dax __free(unpublish_cxl_dax_region) =
> > cxl_dax_region_alloc(cxlr);
> > if (IS_ERR(cxlr_dax))
> > return PTR_ERR(cxlr_dax);
> > diff --git a/drivers/cxl/cxl.h b/drivers/cxl/cxl.h
> > index 64138e1768a1..f7d7749d704c 100644
> > --- a/drivers/cxl/cxl.h
> > +++ b/drivers/cxl/cxl.h
> > @@ -325,6 +325,42 @@ enum cxl_decoder_state {
> > CXL_DECODER_STATE_AUTO_STAGED,
> > };
> >
> > +struct cxl_dc_tag_group;
> > +
> > +/**
> > + * struct dc_extent - A single dynamic-capacity extent surfaced to the host.
> > + *
> > + * One per device-stamped extent. Multiple dc_extents that share a tag
> > + * (see &struct cxl_dc_tag_group) form a single logical allocation, but
> > + * each dc_extent has its own HPA range.
> > + *
> > + * @dev: device representing this extent; child of its tag_groupX.Y
> > + * device, or of the dax_region's untagged device for a null tag.
> > + * @group: tag group that this extent belongs to; shared across siblings.
> > + * @cxled: endpoint decoder backing the DPA range.
> > + * @dpa_range: DPA range this extent covers within @cxled.
> > + * @hpa_range: HPA range that @dpa_range decodes to, relative to
> > + * cxlr_dax->hpa_range.start.
> > + * @uuid: tag uuid (matches @group->uuid).
> > + * @seq_num: 0..n-1 assembly-order index within the tag group. For a
> > + * sharable partition the order follows the shared_extn_seq given
> > + * by the device; for a non-sharable partition, where
> > + * shared_extn_seq is reserved, the order is the order in which
> > + * extents arrive. Either way @seq_num forms a dense range 0..n-1.
> > + * @rcu: rcu_head for the kfree_rcu() deferred free in dc_extent_release(),
> > + * so RCU readers walking the tag group's extents finish safely.
> > + */
> > +struct dc_extent {
> > + struct device dev;
> > + struct cxl_dc_tag_group *group;
> > + struct cxl_endpoint_decoder *cxled;
> > + struct range dpa_range;
> > + struct range hpa_range;
> > + uuid_t uuid;
> > + u16 seq_num;
> > + struct rcu_head rcu;
> > +};
> > +
> > /**
> > * struct cxl_endpoint_decoder - Endpoint / SPA to DPA decoder
> > * @cxld: base cxl_decoder_object
> > @@ -490,6 +526,7 @@ struct cxl_region_params {
> > * @type: Endpoint decoder target type
> > * @cxl_nvb: nvdimm bridge for coordinating @cxlr_pmem setup / shutdown
> > * @cxlr_pmem: (for pmem regions) cached copy of the nvdimm bridge
> > + * @cxlr_dax: the region's cxl_dax_region while it is registered, else NULL
> > * @flags: Region state flags
> > * @shareable: (for DC regions) backing partitions must be shareable
> > * @read_only: (for DC regions) backing partitions must be read-only
> > @@ -508,6 +545,7 @@ struct cxl_region {
> > enum cxl_decoder_type type;
> > struct cxl_nvdimm_bridge *cxl_nvb;
> > struct cxl_pmem_region *cxlr_pmem;
> > + struct cxl_dax_region *cxlr_dax;
> > unsigned long flags;
> > bool shareable;
> > bool read_only;
> > @@ -570,8 +608,57 @@ struct cxl_dax_region {
> > struct device dev;
> > struct cxl_region *cxlr;
> > struct range hpa_range;
> > + /*
> > + * dc_extents is keyed by an allocator-assigned u32 (see
> > + * online_tag_group()). Tag groups have no first-class identity in
> > + * this xarray; siblings within a tag find each other via
> > + * dc_extent->group.
> > + */
> > + struct xarray dc_extents;
> > + /* ids for the tag_groupX.Y devices registered under this region */
> > + struct ida tag_group_ida;
> > + /* parent of the extentX.Y devices of untagged allocations */
> > + struct device untagged;
> > };
> >
> > +/**
> > + * struct cxl_dc_tag_group - A tagged dynamic-capacity allocation.
> > + *
> > + * Container for the &struct dc_extent siblings that share a tag. A
> > + * tagged group is a tag_groupX.Y device under the dax_region and the
> > + * parent of its extentX.Y devices; untagged extents, each a group of
> > + * one, sit under the region's untagged device instead. The group
> > + * exists to keep tag-scoped invariants (atomic add, atomic release,
> > + * ordered carve by seq_num) in one place.
> > + *
> > + * @dev: device representing a tagged group; child of cxlr_dax->dev.
> > + * Holds the group's memory: the last dc_extent release drops the
> > + * final reference. Never registered for an untagged group.
> > + * @cxlr_dax: back reference to parent region device.
> > + * @uuid: tag identifying this allocation; same across all member dc_extents.
> > + * @dc_extents: xarray of &struct dc_extent in this group, indexed by the
> > + * dc_extent's @seq_num (0..n-1, dense). See &struct dc_extent
> > + * for how seq_num is sourced for sharable vs non-sharable
> > + * allocations.
> > + * @nr_extents: live count of dc_extents in the group; the group is freed
> > + * when the last dc_extent device is released.
> > + */
> > +struct cxl_dc_tag_group {
> > + struct device dev;
> > + struct cxl_dax_region *cxlr_dax;
> > + uuid_t uuid;
> > + struct xarray dc_extents;
> > + unsigned int nr_extents;
> > +};
> > +
> > +bool is_dc_extent(struct device *dev);
> > +static inline struct dc_extent *to_dc_extent(struct device *dev)
> > +{
> > + if (!is_dc_extent(dev))
> > + return NULL;
> > + return container_of(dev, struct dc_extent, dev);
> > +}
> > +
> > /**
> > * struct cxl_port - logical collection of upstream port devices and
> > * downstream port devices to construct a CXL memory
> > diff --git a/drivers/cxl/cxlmem.h b/drivers/cxl/cxlmem.h
> > index 52c936ec15a9..73f01efc0172 100644
> > --- a/drivers/cxl/cxlmem.h
> > +++ b/drivers/cxl/cxlmem.h
> > @@ -433,6 +433,7 @@ static inline struct cxl_dev_state *mbox_to_cxlds(struct cxl_mailbox *cxl_mbox)
> > * struct cxl_dc_event_chain - staged Dynamic Capacity event chain
> > * @pending_extents: extents received so far; flushed when the chain
> > * closes (More=0)
> > + * @group: tag group being assembled from an Add Capacity chain
> > * @timeout_work: watchdog that fires if a chain is opened with
> > * CXL_DCD_EVENT_MORE but the closing record never arrives
> > * @lock: serialises updates to the chain state against the watchdog
> > @@ -454,6 +455,7 @@ static inline struct cxl_dev_state *mbox_to_cxlds(struct cxl_mailbox *cxl_mbox)
> > */
> > struct cxl_dc_event_chain {
> > struct list_head pending_extents;
> > + struct cxl_dc_tag_group *group;
> > struct delayed_work timeout_work;
> > struct mutex lock; /* chain state, against the watchdog */
> > bool armed;
> > diff --git a/drivers/dax/bus.c b/drivers/dax/bus.c
> > index d8cc1c012f46..7d28aedfd2f7 100644
> > --- a/drivers/dax/bus.c
> > +++ b/drivers/dax/bus.c
> > @@ -539,6 +539,8 @@ static int alloc_dev_dax_id(struct dev_dax *dev_dax)
> > return id;
> > }
> >
> > +static bool is_dev_dax(struct device *dev);
> > +
> > static ssize_t delete_store(struct device *dev, struct device_attribute *attr,
> > const char *buf, size_t len)
> > {
> > @@ -555,6 +557,12 @@ static ssize_t delete_store(struct device *dev, struct device_attribute *attr,
> > if (!victim)
> > return -ENXIO;
> >
> > + /* Tag groups and the untagged device are children of the region too */
> > + if (!is_dev_dax(victim)) {
> > + put_device(victim);
> > + return -EINVAL;
> > + }
> > +
> > device_lock(dev);
> > device_lock(victim);
> > dev_dax = to_dev_dax(victim);
> > @@ -1443,6 +1451,11 @@ static const struct device_type dev_dax_type = {
> > .groups = dax_attribute_groups,
> > };
> >
> > +static bool is_dev_dax(struct device *dev)
> > +{
> > + return dev->type == &dev_dax_type;
> > +}
> > +
> > /* see "strong" declaration in tools/testing/nvdimm/dax-dev.c */
> > __weak phys_addr_t dax_pgoff_to_phys(struct dev_dax *dev_dax, pgoff_t pgoff,
> > unsigned long size)
> > diff --git a/tools/testing/cxl/Kbuild b/tools/testing/cxl/Kbuild
> > index e49ce644b4b1..f1ab25872e76 100644
> > --- a/tools/testing/cxl/Kbuild
> > +++ b/tools/testing/cxl/Kbuild
> > @@ -67,7 +67,10 @@ cxl_core-y += $(CXL_CORE_SRC)/hdm.o
> > cxl_core-y += $(CXL_CORE_SRC)/pmu.o
> > cxl_core-y += $(CXL_CORE_SRC)/cdat.o
> > cxl_core-$(CONFIG_TRACING) += $(CXL_CORE_SRC)/trace.o
> > -cxl_core-$(CONFIG_CXL_REGION) += $(CXL_CORE_SRC)/region.o $(CXL_CORE_SRC)/region_pmem.o $(CXL_CORE_SRC)/region_dax.o
> > +cxl_core-$(CONFIG_CXL_REGION) += $(CXL_CORE_SRC)/region.o \
> > + $(CXL_CORE_SRC)/region_pmem.o \
> > + $(CXL_CORE_SRC)/region_dax.o \
> > + $(CXL_CORE_SRC)/extent.o
> > cxl_core-$(CONFIG_CXL_MCE) += $(CXL_CORE_SRC)/mce.o
> > cxl_core-$(CONFIG_CXL_FEATURES) += $(CXL_CORE_SRC)/features.o
> > cxl_core-$(CONFIG_CXL_EDAC_MEM_FEATURES) += $(CXL_CORE_SRC)/edac.o
> > --
> > 2.43.0
> >
next prev parent reply other threads:[~2026-11-16 21:51 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 23:02 [PATCH v1 00/14] DCD CXL Series: Dynamic Capacity extent handling Anisa Su
2026-11-04 23:02 ` [PATCH v1 01/14] cxl/core: Return endpoint decoder information from region search Anisa Su
2026-11-04 23:02 ` [PATCH v1 02/14] cxl/port: Add dynamic capacity options to endpoint decoder mode Anisa Su
2026-11-04 23:02 ` [PATCH v1 03/14] cxl/region: Add dynamic DAX region support Anisa Su
2026-11-04 23:02 ` [PATCH v1 04/14] cxl/mem: Introduce DC event handlers Anisa Su
2026-11-04 23:02 ` [PATCH v1 05/14] cxl/mem: Add 20 second timeout for stalled DC event chains Anisa Su
2026-11-04 23:02 ` [PATCH v1 06/14] cxl/extent: Handle DC Add Capacity events Anisa Su
2026-11-12 3:34 ` Richard Cheng
2026-11-16 21:53 ` Anisa Su [this message]
2026-11-04 23:02 ` [PATCH v1 07/14] cxl/mem: Drop misaligned DCD extent groups Anisa Su
2026-11-04 23:02 ` [PATCH v1 08/14] cxl/extent: Validate DC extent partition Anisa Su
2026-11-04 23:02 ` [PATCH v1 09/14] cxl/mem: Enforce tag-group semantics Anisa Su
2026-11-04 23:02 ` [PATCH v1 10/14] cxl/extent: Enforce cross-region tag uniqueness Anisa Su
2026-11-04 23:02 ` [PATCH v1 11/14] cxl/extent: Handle DC Release Capacity events Anisa Su
2026-11-12 7:34 ` Richard Cheng
2026-11-04 23:02 ` [PATCH v1 12/14] cxl/region: Read existing extents on region creation Anisa Su
2026-11-04 23:02 ` [PATCH v1 13/14] cxl/mem: Trace Dynamic capacity Event Record Anisa Su
2026-11-04 23:02 ` [PATCH v1 14/14] Documentation/cxl: Document DCD extent handling 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=avt7ZWXUvp9JrO80@cxlqual \
--to=anisa.su887@gmail.com \
--cc=alison.schofield@intel.com \
--cc=benjamin.cheatham@amd.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=gourry@gourry.net \
--cc=icheng@nvidia.com \
--cc=iweiny@kernel.org \
--cc=jic23@kernel.org \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ming.li@zohomail.com \
--cc=nifan.cxl@gmail.com \
--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®