From: Davidlohr Bueso <dave@stgolabs.net>
To: Ira Weiny <ira.weiny@intel.com>
Cc: Dave Jiang <dave.jiang@intel.com>, Fan Ni <fan.ni@samsung.com>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
Dan Williams <dan.j.williams@intel.com>,
Alison Schofield <alison.schofield@intel.com>,
Vishal Verma <vishal.l.verma@intel.com>,
linux-cxl@vger.kernel.org, nvdimm@lists.linux.dev,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v9 16/19] cxl/region: Read existing extents on region creation
Date: Mon, 2 Feb 2026 11:42:45 -0800 [thread overview]
Message-ID: <20260202194245.7wmk64v4l4pdf2hc@offworld> (raw)
In-Reply-To: <20250413-dcd-type2-upstream-v9-16-1d4911a0b365@intel.com>
On Sun, 13 Apr 2025, Ira Weiny wrote:
>Dynamic capacity device extents may be left in an accepted state on a
>device due to an unexpected host crash. In this case it is expected
>that the creation of a new region on top of a DC partition can read
>those extents and surface them for continued use.
>
>Once all endpoint decoders are part of a region and the region is being
>realized, a read of the 'devices extent list' can reveal these
>previously accepted extents.
>
>CXL r3.1 specifies the mailbox call Get Dynamic Capacity Extent List for
>this purpose. The call returns all the extents for all dynamic capacity
>partitions. If the fabric manager is adding extents to any DCD
>partition, the extent list for the recovered region may change. In this
>case the query must retry. Upon retry the query could encounter extents
>which were accepted on a previous list query. Adding such extents is
>ignored without error because they are entirely within a previous
>accepted extent. Instead warn on this case to allow for differentiating
>bad devices from this normal condition.
>
>Latch any errors to be bubbled up to ensure notification to the user
>even if individual errors are rate limited or otherwise ignored.
>
>The scan for existing extents races with the dax_cxl driver. This is
>synchronized through the region device lock. Extents which are found
>after the driver has loaded will surface through the normal notification
>path while extents seen prior to the driver are read during driver load.
>
>Based on an original patch by Navneet Singh.
>
>Reviewed-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>Reviewed-by: Fan Ni <fan.ni@samsung.com>
>Signed-off-by: Ira Weiny <ira.weiny@intel.com>
>
>---
>Changes:
>[0day: fix extent count in GetExtent input payload]
>[iweiny: minor clean ups]
>[iweiny: Adjust for partition arch]
>---
> drivers/cxl/core/core.h | 1 +
> drivers/cxl/core/mbox.c | 109 ++++++++++++++++++++++++++++++++++++++++++++++
> drivers/cxl/core/region.c | 25 +++++++++++
> drivers/cxl/cxlmem.h | 21 +++++++++
> 4 files changed, 156 insertions(+)
>
>diff --git a/drivers/cxl/core/core.h b/drivers/cxl/core/core.h
>index 027dd1504d77..e06a46fec217 100644
>--- a/drivers/cxl/core/core.h
>+++ b/drivers/cxl/core/core.h
>@@ -22,6 +22,7 @@ cxled_to_mds(struct cxl_endpoint_decoder *cxled)
> return container_of(cxlds, struct cxl_memdev_state, cxlds);
> }
>
>+int cxl_process_extent_list(struct cxl_endpoint_decoder *cxled);
> int cxl_region_invalidate_memregion(struct cxl_region *cxlr);
>
> #ifdef CONFIG_CXL_REGION
>diff --git a/drivers/cxl/core/mbox.c b/drivers/cxl/core/mbox.c
>index de01c6684530..8af3a4173b99 100644
>--- a/drivers/cxl/core/mbox.c
>+++ b/drivers/cxl/core/mbox.c
>@@ -1737,6 +1737,115 @@ int cxl_dev_dc_identify(struct cxl_mailbox *mbox,
> }
> EXPORT_SYMBOL_NS_GPL(cxl_dev_dc_identify, "CXL");
>
>+/* Return -EAGAIN if the extent list changes while reading */
>+static int __cxl_process_extent_list(struct cxl_endpoint_decoder *cxled)
>+{
>+ u32 current_index, total_read, total_expected, initial_gen_num;
>+ struct cxl_memdev_state *mds = cxled_to_mds(cxled);
>+ struct cxl_mailbox *cxl_mbox = &mds->cxlds.cxl_mbox;
>+ struct device *dev = mds->cxlds.dev;
>+ struct cxl_mbox_cmd mbox_cmd;
>+ u32 max_extent_count;
>+ int latched_rc = 0;
>+ bool first = true;
>+
>+ struct cxl_mbox_get_extent_out *extents __free(kvfree) =
>+ kvmalloc(cxl_mbox->payload_size, GFP_KERNEL);
>+ if (!extents)
>+ return -ENOMEM;
>+
>+ total_read = 0;
>+ current_index = 0;
>+ total_expected = 0;
>+ max_extent_count = (cxl_mbox->payload_size - sizeof(*extents)) /
>+ sizeof(struct cxl_extent);
>+ do {
>+ u32 nr_returned, current_total, current_gen_num;
>+ struct cxl_mbox_get_extent_in get_extent;
>+ int rc;
>+
>+ get_extent = (struct cxl_mbox_get_extent_in) {
>+ .extent_cnt = cpu_to_le32(max(max_extent_count,
>+ total_expected - current_index)),
s/max/min().
>+ .start_extent_index = cpu_to_le32(current_index),
next prev parent reply other threads:[~2026-02-02 19:42 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-13 22:52 [PATCH v9 00/19] DCD: Add support for Dynamic Capacity Devices (DCD) Ira Weiny
2025-04-13 22:52 ` [PATCH v9 01/19] cxl/mbox: Flag " Ira Weiny
2025-04-14 14:19 ` Jonathan Cameron
2025-05-05 21:04 ` Fan Ni
2025-05-06 16:09 ` Ira Weiny
2025-05-06 18:54 ` Fan Ni
2025-04-13 22:52 ` [PATCH v9 02/19] cxl/mem: Read dynamic capacity configuration from the device Ira Weiny
2025-04-14 14:35 ` Jonathan Cameron
2025-04-14 15:20 ` Jonathan Cameron
2025-05-07 17:40 ` Fan Ni
2025-05-08 13:35 ` Ira Weiny
2025-04-13 22:52 ` [PATCH v9 03/19] cxl/cdat: Gather DSMAS data for DCD partitions Ira Weiny
2025-04-14 15:29 ` Jonathan Cameron
2025-04-13 22:52 ` [PATCH v9 04/19] cxl/core: Enforce partition order/simplify partition calls Ira Weiny
2025-04-14 15:32 ` Jonathan Cameron
2026-02-02 19:25 ` Davidlohr Bueso
2025-04-13 22:52 ` [PATCH v9 05/19] cxl/mem: Expose dynamic ram A partition in sysfs Ira Weiny
2025-04-14 15:34 ` Jonathan Cameron
2026-02-02 19:28 ` Davidlohr Bueso
2025-04-13 22:52 ` [PATCH v9 06/19] cxl/port: Add 'dynamic_ram_a' to endpoint decoder mode Ira Weiny
2025-04-14 15:36 ` Jonathan Cameron
2025-05-07 20:50 ` Fan Ni
2025-04-13 22:52 ` [PATCH v9 07/19] cxl/region: Add sparse DAX region support Ira Weiny
2025-04-14 15:40 ` Jonathan Cameron
2025-05-08 17:54 ` Fan Ni
2025-05-08 18:17 ` Fan Ni
2025-04-13 22:52 ` [PATCH v9 08/19] cxl/events: Split event msgnum configuration from irq setup Ira Weiny
2025-04-13 22:52 ` [PATCH v9 09/19] cxl/pci: Factor out interrupt policy check Ira Weiny
2025-04-13 22:52 ` [PATCH v9 10/19] cxl/mem: Configure dynamic capacity interrupts Ira Weiny
2025-04-13 22:52 ` [PATCH v9 11/19] cxl/core: Return endpoint decoder information from region search Ira Weiny
2025-04-13 22:52 ` [PATCH v9 12/19] cxl/extent: Process dynamic partition events and realize region extents Ira Weiny
2025-04-14 16:07 ` Jonathan Cameron
2025-04-14 22:10 ` Alison Schofield
2025-05-12 17:47 ` Fan Ni
2026-02-02 20:00 ` Davidlohr Bueso
2026-02-24 1:24 ` Anisa Su
2026-03-05 22:00 ` Ira Weiny
2025-04-13 22:52 ` [PATCH v9 13/19] cxl/region/extent: Expose region extent information in sysfs Ira Weiny
2025-04-13 22:52 ` [PATCH v9 14/19] dax/bus: Factor out dev dax resize logic Ira Weiny
2025-04-13 22:52 ` [PATCH v9 15/19] dax/region: Create resources on sparse DAX regions Ira Weiny
2025-04-13 22:52 ` [PATCH v9 16/19] cxl/region: Read existing extents on region creation Ira Weiny
2025-04-14 16:15 ` Jonathan Cameron
2026-02-02 19:42 ` Davidlohr Bueso [this message]
2025-04-13 22:52 ` [PATCH v9 17/19] cxl/mem: Trace Dynamic capacity Event Record Ira Weiny
2025-04-13 22:52 ` [PATCH v9 18/19] tools/testing/cxl: Make event logs dynamic Ira Weiny
2025-04-13 22:52 ` [PATCH v9 19/19] tools/testing/cxl: Add DC Regions to mock mem data Ira Weiny
2025-04-14 16:11 ` [PATCH v9 00/19] DCD: Add support for Dynamic Capacity Devices (DCD) Fan Ni
2025-04-15 2:37 ` Ira Weiny
2025-04-15 2:47 ` Fan Ni
2025-04-15 4:28 ` Dan Williams
2025-05-13 18:55 ` Fan Ni
2025-04-14 16:47 ` Jonathan Cameron
2025-04-15 4:50 ` Dan Williams
2025-04-15 10:03 ` Jonathan Cameron
2025-04-15 17:45 ` Dan Williams
2025-06-03 16:32 ` Fan Ni
2025-06-09 17:09 ` Fan Ni
2026-02-02 20:22 ` Gregory Price
2026-02-03 22:04 ` Ira Weiny
2026-02-04 15:12 ` Gregory Price
2026-02-04 17:57 ` Ira Weiny
2026-02-04 18:53 ` Gregory Price
2026-02-05 17:48 ` Jonathan Cameron
2026-02-06 11:01 ` Alireza Sanaee
2026-02-06 13:26 ` 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=20260202194245.7wmk64v4l4pdf2hc@offworld \
--to=dave@stgolabs.net \
--cc=Jonathan.Cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=fan.ni@samsung.com \
--cc=ira.weiny@intel.com \
--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®