From: Neeraj Kumar <s.neeraj@samsung.com>
To: Jonathan Cameron <Jonathan.Cameron@huawei.com>
Cc: dan.j.williams@intel.com, dave@stgolabs.net,
dave.jiang@intel.com, alison.schofield@intel.com,
vishal.l.verma@intel.com, ira.weiny@intel.com,
a.manzanares@samsung.com, nifan.cxl@gmail.com,
anisa.su@samsung.com, vishak.g@samsung.com,
krish.reddy@samsung.com, arun.george@samsung.com,
alok.rathore@samsung.com, neeraj.kernel@gmail.com,
linux-kernel@vger.kernel.org, linux-cxl@vger.kernel.org,
nvdimm@lists.linux.dev, gost.dev@samsung.com, cpgs@samsung.com
Subject: Re: [RFC PATCH 14/20] cxl/region: Add cxl pmem region creation routine for region persistency
Date: Thu, 26 Jun 2025 15:53:41 +0530 [thread overview]
Message-ID: <700072760.81750944183483.JavaMail.epsvc@epcpadp2new> (raw)
In-Reply-To: <20250623104302.00004405@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 8221 bytes --]
On 23/06/25 10:43AM, Jonathan Cameron wrote:
>On Tue, 17 Jun 2025 18:09:38 +0530
>Neeraj Kumar <s.neeraj@samsung.com> wrote:
>
>> Added exported cxl_create_pmem_region routine to create cxl pmem region
>
>For function names always add () after and drop 'function/routine' etc.
>Ends up shorter and easier to read.
>
Sure, Will fix it accordingly
>> from LSA parsed cxl region information.
>> Inspirition for the function is taken from ndctl device attribute
>> (_store) call. It allocates cxlr and fills information parsed from LSA
>> and calls device_add(&cxlr->dev) to initiates further region creation
>> porbes
>Spell check.
>
Thanks, Will fix it up.
>>
>> Signed-off-by: Neeraj Kumar <s.neeraj@samsung.com>
>> ---
>> drivers/cxl/core/port.c | 6 ++
>> drivers/cxl/core/region.c | 208 ++++++++++++++++++++++++++++++++++++++
>> drivers/cxl/cxl.h | 11 ++
>> 3 files changed, 225 insertions(+)
>>
>
>> diff --git a/drivers/cxl/core/region.c b/drivers/cxl/core/region.c
>> index b98b1ccffd1c..8990e3c3474d 100644
>> --- a/drivers/cxl/core/region.c
>> +++ b/drivers/cxl/core/region.c
>> @@ -2522,6 +2522,214 @@ static ssize_t create_ram_region_show(struct device *dev,
>> return __create_region_show(to_cxl_root_decoder(dev), buf);
>> }
>>
>> +static ssize_t update_region_size(struct cxl_region *cxlr, u64 val)
>> +{
>> + int rc;
>> +
>> + rc = down_write_killable(&cxl_region_rwsem);
>ACQUIRE() as mentioned below.
>
Sure, Let me look at Dan's new ACQUIRE() series. I will update it in V1
>> + if (rc)
>> + return rc;
>> +
>> + if (val)
>> + rc = alloc_hpa(cxlr, val);
>> + else
>> + rc = free_hpa(cxlr);
>> + up_write(&cxl_region_rwsem);
>> +
>> + if (rc)
>> + return rc;
>
> return rc;
>
Thanks, I will update it.
>> +
>> + return 0;
>> +}
>> +
>> +static ssize_t update_region_dpa_size(struct cxl_region *cxlr,
>> + struct cxl_decoder *cxld,
>> + unsigned long long size)
>> +{
>> + int rc;
>> + struct cxl_endpoint_decoder *cxled =
>> + to_cxl_endpoint_decoder(&cxld->dev);
>> +
>> + if (!IS_ALIGNED(size, SZ_256M))
>> + return -EINVAL;
>> +
>> + rc = cxl_dpa_free(cxled);
>> + if (rc)
>> + return rc;
>> +
>> + if (size == 0)
>> + return 0;
>> +
>> + rc = cxl_dpa_alloc(cxled, size);
>return cxl_dpa_alloc()
>
>Unless something more is getting added here in later patches in which case
>you can ignore this comment.
>
Thanks, Will fix it accordingly
>> + if (rc)
>> + return rc;
>> +
>> + return 0;
>> +}
>> +
>> +static ssize_t update_region_dpa_mode(struct cxl_region *cxlr,
>> + struct cxl_decoder *cxld)
>> +{
>> + int rc;
>> + struct cxl_endpoint_decoder *cxled =
>> + to_cxl_endpoint_decoder(&cxld->dev);
>Maybe don't bother with local variable and just put this
>below as the parameter.
Sure, I will fix it.
>> +
>> + rc = cxl_dpa_set_mode(cxled, CXL_DECODER_PMEM);
>
>return cxl_dpa_set_mode()
>
>> + if (rc)
>> + return rc;
>> +
>> + return 0;
>> +}
>> +
>> +static size_t attach_region_target(struct cxl_region *cxlr,
>> + struct cxl_decoder *cxld, int pos)
>> +{
>> + int rc;
>> + struct cxl_endpoint_decoder *cxled =
>> + to_cxl_endpoint_decoder(&cxld->dev);
>> +
>> + rc = attach_target(cxlr, cxled, pos, TASK_INTERRUPTIBLE);
>> +
>No blank line here
Sure, I will fix it.
>> + if (rc < 0)
>Can it ever be > 0 ?
>If not, return attach_target() should be fine.
Yes we can directly return from here, will fix it in V1
>> + return rc;
>> +
>> + return 0;
>> +}
>> +
>> +static ssize_t commit_region(struct cxl_region *cxlr)
>> +{
>> + struct cxl_region_params *p = &cxlr->params;
>> + ssize_t rc;
>> +
>> + rc = down_write_killable(&cxl_region_rwsem);
>
>Maybe look at Dan's new ACQUIRE() series. The last patch in there
>is targeting code similar to this.
Sure, Let me look at Dan's new ACQUIRE() series. I will update it in V1
>
>> + if (rc)
>> + return rc;
>> +
>> + /* Already in the requested state? */
>> + if (p->state >= CXL_CONFIG_COMMIT)
>> + goto out;
>> +
>> + /* Not ready to commit? */
>> + if (p->state < CXL_CONFIG_ACTIVE) {
>> + rc = -ENXIO;
>> + goto out;
>> + }
>> +
>> + /*
>> + * Invalidate caches before region setup to drop any speculative
>> + * consumption of this address space
>> + */
>> + rc = cxl_region_invalidate_memregion(cxlr);
>> + if (rc)
>> + goto out;
>> +
>> + rc = cxl_region_decode_commit(cxlr);
>> + if (rc == 0)
>With AQUIRE() stuff you can just do
> if (rc)
> return rc;
>
>here
>
Thanks, Will update it accordingly.
>> + p->state = CXL_CONFIG_COMMIT;
>> +out:
>> + up_write(&cxl_region_rwsem);
>> + if (rc)
>> + return rc;
>> + return 0;
>> +}
>> +
>> +static struct cxl_region *
>> +devm_cxl_pmem_add_region(struct cxl_root_decoder *cxlrd,
>> + struct cxl_decoder *cxld,
>> + struct cxl_pmem_region_params *params, int id,
>> + enum cxl_decoder_mode mode, enum cxl_decoder_type type)
>> +{
>> + struct cxl_port *port;
>> + struct cxl_region *cxlr;
>> + struct cxl_region_params *p;
>> + struct device *dev;
>> + int rc;
>> +
>> + if (!cxlrd)
>> + return ERR_PTR(-EINVAL);
>
>For a check like this, add a comment on why it might be NULL.
>If it can't be, then drop the check.
>
Sure, I will fix it in V1
>> +
>> + port = to_cxl_port(cxlrd->cxlsd.cxld.dev.parent);
>
>Maybe add a comment on which port this actually is. These long indirections
>can make that hard to figure out!
>
Sure, I will fix it in V1
>> +
>> + cxlr = cxl_region_alloc(cxlrd, id);
>> + if (IS_ERR(cxlr))
>> + return cxlr;
>> + cxlr->mode = mode;
>> + cxlr->type = type;
>> +
>> + dev = &cxlr->dev;
>> + rc = dev_set_name(dev, "region%d", id);
>> + if (rc)
>> + goto err;
>> +
>> + p = &cxlr->params;
>> + p->uuid = params->uuid;
>> + p->interleave_ways = params->nlabel;
>> + p->interleave_granularity = params->ig;
>> +
>> + /* Update region size */
>> + if (update_region_size(cxlr, params->rawsize))
>> + goto err;
>> +
>> + /* Flush cxl wq */
>
>Much more useful to say 'why' you are flushing it. It's obvious
>from the code that you are.
>
Sure Will update the comment properly
>> + cxl_wq_flush();
>> +
>> + /* Clear DPA Size */
>
>I'd look at all these comments and where they are obvious, drop the comment
>and let the code speak for itself.
>
Sure, Will update accordingly
>> + if (update_region_dpa_size(cxlr, cxld, 0))
>> + goto err;
>> +
>> + /* Update DPA mode */
>> + if (update_region_dpa_mode(cxlr, cxld))
>> + goto err;
>> +
>> + /* Update DPA Size */
>> + if (update_region_dpa_size(cxlr, cxld, params->rawsize))
>> + goto err;
>> +
>> + /* Attach region targets */
>It's attaching just one by the look of it. I'd just drop the comment.
>
Sure, Will update accordingly
>> + if (attach_region_target(cxlr, cxld, params->position))
>> + goto err;
>> +
>> + /* Commit Region */
>> + if (commit_region(cxlr))
>> + goto err;
>> +
>> + rc = device_add(dev);
>> + if (rc)
>> + goto err;
>> +
>> + rc = devm_add_action_or_reset(port->uport_dev, unregister_region, cxlr);
>> + if (rc)
>> + return ERR_PTR(rc);
>> +
>> + dev_dbg(port->uport_dev, "%s: created %s\n",
>> + dev_name(&cxlrd->cxlsd.cxld.dev), dev_name(dev));
>> + return cxlr;
>> +
>> +err:
>> + put_device(dev);
>> + return ERR_PTR(rc);
>> +}
>> +
>> +struct cxl_region *cxl_create_pmem_region(struct cxl_root_decoder *cxlrd,
>> + struct cxl_decoder *cxld,
>> + struct cxl_pmem_region_params *params, int id)
>> +{
>> + int rc;
>> +
>> + rc = memregion_alloc(GFP_KERNEL);
>> + if (rc < 0)
>> + return ERR_PTR(rc);
>> +
>> + if (atomic_cmpxchg(&cxlrd->region_id, id, rc) != id) {
>> + memregion_free(rc);
>> + return ERR_PTR(-EBUSY);
>> + }
>I'm a little surprised not to see cleanup of the memregion via
>devm somewhere here.
Actually its cleanup is happening at cxl_region_release().
During cxl_region_alloc, cxlr is allocated whose dev->type is
cxl_region_type
const struct device_type cxl_region_type = {
.name = "cxl_region",
.release = cxl_region_release,
.groups = region_groups
};
>> +
>> + return devm_cxl_pmem_add_region(cxlrd, cxld, params, id,
>> + CXL_DECODER_PMEM, CXL_DECODER_HOSTONLYMEM);
>> +}
>> +EXPORT_SYMBOL_NS_GPL(cxl_create_pmem_region, "CXL");
>> +
>> static struct cxl_region *__create_region(struct cxl_root_decoder *cxlrd,
>> enum cxl_decoder_mode mode, int id)
>> {
>
>
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2025-06-26 13:23 UTC|newest]
Thread overview: 66+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20250617124008epcas5p2e702f786645d44ceb1cdd980a914ce8e@epcas5p2.samsung.com>
[not found] ` <20250617123944.78345-1-s.neeraj@samsung.com>
2025-06-17 12:39 ` [RFC PATCH 01/20] nvdimm/label: Introduce NDD_CXL_LABEL flag to set cxl label format Neeraj Kumar
2025-06-20 16:40 ` Jonathan Cameron
2025-06-26 9:48 ` Neeraj Kumar
2025-07-02 18:02 ` Ira Weiny
2025-07-03 9:58 ` Neeraj Kumar
2025-07-09 22:57 ` Dave Jiang
2025-07-18 12:13 ` Neeraj Kumar
2025-06-17 12:39 ` [RFC PATCH 02/20] nvdimm/label: Prep patch to accommodate cxl lsa 2.1 support Neeraj Kumar
2025-06-23 10:53 ` Jonathan Cameron
2025-06-26 9:51 ` Neeraj Kumar
2025-07-02 17:55 ` Ira Weiny
2025-07-03 10:04 ` Neeraj Kumar
2025-06-17 12:39 ` [RFC PATCH 03/20] nvdimm/namespace_label: Add namespace label changes as per CXL LSA v2.1 Neeraj Kumar
2025-06-17 12:39 ` [RFC PATCH 04/20] nvdimm/label: CXL labels skip the need for 'interleave-set cookie' Neeraj Kumar
2025-06-17 12:39 ` [RFC PATCH 05/20] nvdimm/region_label: Add region label updation routine Neeraj Kumar
2025-06-23 9:05 ` Jonathan Cameron
2025-06-26 9:54 ` Neeraj Kumar
2025-07-17 22:53 ` Fabio M. De Francesco
2025-07-18 13:00 ` Neeraj Kumar
2025-06-17 12:39 ` [RFC PATCH 06/20] nvdimm/region_label: Add region label deletion routine Neeraj Kumar
2025-06-23 9:09 ` Jonathan Cameron
2025-06-26 9:55 ` Neeraj Kumar
2025-06-17 12:39 ` [RFC PATCH 07/20] nvdimm/namespace_label: Update namespace init_labels and its region_uuid Neeraj Kumar
2025-06-23 9:11 ` Jonathan Cameron
2025-06-26 9:58 ` Neeraj Kumar
2025-06-17 12:39 ` [RFC PATCH 08/20] nvdimm/label: Include region label in slot validation Neeraj Kumar
2025-06-23 9:13 ` Jonathan Cameron
2025-06-26 10:00 ` Neeraj Kumar
2025-06-17 12:39 ` [RFC PATCH 09/20] nvdimm/namespace_label: Skip region label during ns label DPA reservation Neeraj Kumar
2025-06-17 12:39 ` [RFC PATCH 10/20] nvdimm/region_label: Preserve cxl region information from region label Neeraj Kumar
2025-06-17 12:39 ` [RFC PATCH 11/20] nvdimm/region_label: Export routine to fetch region information Neeraj Kumar
2025-06-17 12:39 ` [RFC PATCH 12/20] nvdimm/namespace_label: Skip region label during namespace creation Neeraj Kumar
2025-06-23 9:17 ` Jonathan Cameron
2025-06-26 10:02 ` Neeraj Kumar
2025-06-17 12:39 ` [RFC PATCH 13/20] cxl/mem: Refactor cxl pmem region auto-assembling Neeraj Kumar
2025-06-23 9:20 ` Jonathan Cameron
2025-06-26 10:03 ` Neeraj Kumar
2025-07-10 0:38 ` Dave Jiang
2025-07-18 12:30 ` Neeraj Kumar
2025-07-21 18:11 ` Dave Jiang
2025-06-17 12:39 ` [RFC PATCH 14/20] cxl/region: Add cxl pmem region creation routine for region persistency Neeraj Kumar
2025-06-23 9:43 ` Jonathan Cameron
2025-06-26 10:23 ` Neeraj Kumar [this message]
2025-07-10 15:59 ` Dave Jiang
2025-07-18 12:45 ` Neeraj Kumar
2025-06-17 12:39 ` [RFC PATCH 15/20] cxl: Add a routine to find cxl root decoder on cxl bus Neeraj Kumar
2025-06-23 9:44 ` Jonathan Cameron
2025-06-26 10:38 ` Neeraj Kumar
2025-06-26 19:19 ` Alison Schofield
2025-06-27 9:03 ` Neeraj Kumar
2025-07-10 16:23 ` Dave Jiang
2025-07-18 12:48 ` Neeraj Kumar
2025-06-17 12:39 ` [RFC PATCH 16/20] cxl/mem: Preserve cxl root decoder during mem probe Neeraj Kumar
2025-06-17 12:39 ` [RFC PATCH 17/20] cxl/pmem: Preserve region information into nd_set Neeraj Kumar
2025-06-17 12:39 ` [RFC PATCH 18/20] cxl/pmem: Add support of cxl lsa 2.1 support in cxl pmem Neeraj Kumar
2025-06-23 9:48 ` Jonathan Cameron
2025-06-26 10:41 ` Neeraj Kumar
2025-07-10 17:18 ` Dave Jiang
2025-07-18 12:51 ` Neeraj Kumar
2025-07-21 17:44 ` Dave Jiang
2025-06-17 12:39 ` [RFC PATCH 19/20] cxl/pmem_region: Prep patch to accommodate pmem_region attributes Neeraj Kumar
2025-06-23 9:53 ` Jonathan Cameron
2025-06-26 10:45 ` Neeraj Kumar
2025-06-17 12:39 ` [RFC PATCH 20/20] cxl/pmem_region: Add cxl region label updation and deletion device attributes Neeraj Kumar
2025-06-23 9:56 ` Jonathan Cameron
2025-06-26 10:48 ` Neeraj Kumar
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=700072760.81750944183483.JavaMail.epsvc@epcpadp2new \
--to=s.neeraj@samsung.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=a.manzanares@samsung.com \
--cc=alison.schofield@intel.com \
--cc=alok.rathore@samsung.com \
--cc=anisa.su@samsung.com \
--cc=arun.george@samsung.com \
--cc=cpgs@samsung.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=gost.dev@samsung.com \
--cc=ira.weiny@intel.com \
--cc=krish.reddy@samsung.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=neeraj.kernel@gmail.com \
--cc=nifan.cxl@gmail.com \
--cc=nvdimm@lists.linux.dev \
--cc=vishak.g@samsung.com \
--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