From: "Paweł Mielimonka" <pawel.mielimonka@gmail.com>
To: Alison Schofield <alison.schofield@intel.com>,
Pawel Mielimonka <pawel.mielimonka@fujitsu.com>
Cc: dan.j.williams@intel.com, Smita.KoralahalliChannabasappa@amd.com,
linux-cxl@vger.kernel.org, linux-kernel@vger.kernel.org,
dave@stgolabs.net, jonathan.cameron@huawei.com,
dave.jiang@intel.com, vishal.l.verma@intel.com,
ira.weiny@intel.com
Subject: [RFC PATCH v1 1/2] cxl/cli: add helpers to collect and sort regions by HPA
Date: Wed, 3 Dec 2025 10:09:15 +0100 [thread overview]
Message-ID: <7eaf281d-6b92-4d8b-a633-e81925116364@gmail.com> (raw)
In-Reply-To: <aS-0DNw3Jnw4ZR-y@aschofie-mobl2.lan>
W dniu 3.12.2025 o 04:52, Alison Schofield pisze:
> On Tue, Nov 25, 2025 at 11:38:23PM +0900, Pawel Mielimonka wrote:
>> Introduce cmp_region_hpa() and collect_regions_sorted() helpers to
>> enumerate CXL regions under a given decoder and sort them by their host
>> physical address.
>> These helpers will be used by the "cxl destroy-region" command to tear
>> down regions in HPA-descending order, i.e. in the reverse order of
>> region creation. This matches the decoder programming requirements from
>> the CXL specification (8.2.4.20.12 - continuous HPA coverage at all
>> times when Lock On Commit is used) and avoids teardown sequences that
>> can leve decoder state inconsistent when the decoder is fully populated
>> (known problem).
>> This patch only adds the helpers; no functional changes is intended yet.
>>
>> Signed-off-by: Pawel Mielimonka <pawel.mielimonka@fujitsu.com>
>> ---
>> cxl/region.c | 55 ++++++++++++++++++++++++++++++++++++++++++++++++++++
>> 1 file changed, 55 insertions(+)
>>
>> diff --git a/cxl/region.c b/cxl/region.c
>> index 207cf2d0..58765b3d 100644
>> --- a/cxl/region.c
>> +++ b/cxl/region.c
>> @@ -831,6 +831,61 @@ out:
>> return cxl_region_disable(region);
>> }
>>
>> +static int cmp_region_hpa(const void *l, const void *r)
>> +{
>> + const struct cxl_region *const *left = l;
>> + const struct cxl_region *const *right = r;
>> + u64 left_start = cxl_region_get_resource((struct cxl_region *) *left);
>> + u64 right_start = cxl_region_get_resource((struct cxl_region *) *right);
>> +
>> + if (left_start < right_start)
>> + return -1;
>> + if (left_start > right_start)
>> + return 1;
> Suggest calling them hpa's and using this more common kernel compare pattern.
> (yeah, in ndctl, cxl/cli, we try to be like kernel)
>
> static int cmp_region_hpa(const void *a, const void *b)
> {
> const struct cxl_region *const *r1 = a;
> const struct cxl_region *const *r2 = b;
> u64 hpa1 = cxl_region_get_resource((struct cxl_region *) *r1);
> u64 hpa2 = cxl_region_get_resource((struct cxl_region *) *r2);
>
> return (hpa1 > hpa2) - (hpa1 < hpa2);
> }
I followed the pattern in region.c but you're right, I'll fix it in v2.
>
>> + return 0;
>> +}
>> +
>> +static int collect_regions_sorted(struct cxl_decoder *root,
>> + const char *filter,
>> + struct cxl_region ***out,
>> + int *out_nr)
>> +{
> I think there is an alignment issue above.
> The filter parameter is always called w NULL in patcht 2.
> If it's not going to be used, remove it.
>
>> + struct cxl_region *region;
>> + struct cxl_region **list = NULL;
>> + int nr = 0, alloc = 0;
>> +
>> + cxl_region_foreach(root, region) {
>> + if (filter && !util_cxl_region_filter(region, filter))
>> + continue;
>> + if (nr == alloc) {
>> + int new_alloc = alloc ? alloc * 2 : 8;
>> + int new_size = (size_t)new_alloc * sizeof(*list);
> Looks like new_size should be size_t to match what realloc() expects.
Both changes I'll make in v2. Thanks for noticing.
>
>> + struct cxl_region **tmp;
>> +
>> + tmp = realloc(list, new_size);
>> + if (!tmp) {
>> + free(list);
>> + return -ENOMEM;
>> + }
>> + list = tmp;
>> + alloc = new_alloc;
>> + }
>> + list[nr++] = region;
>> + }
>> +
>> + if (!nr) {
>> + free(list);
>> + *out = NULL;
>> + *out_nr = 0;
>> + return 0;
>> + }
>> +
>> + qsort(list, nr, sizeof(*list), cmp_region_hpa);
>> + *out = list;
>> + *out_nr = nr;
>> + return 0;
>> +}
>> +
>> static int destroy_region(struct cxl_region *region)
>> {
>> const char *devname = cxl_region_get_devname(region);
>> --
>> 2.45.1.windows.1
>>
next prev parent reply other threads:[~2025-12-03 9:09 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-25 14:38 [RFC PATCH v1 0/2] cxl/cli: HPA-ordered destroy-region teardown Pawel Mielimonka
2025-11-25 14:38 ` [RFC PATCH v1 1/2] cxl/cli: add helpers to collect and sort regions by HPA Pawel Mielimonka
2025-12-03 3:52 ` Alison Schofield
2025-12-03 9:09 ` Paweł Mielimonka [this message]
2025-11-25 14:38 ` [RFC PATCH v1 2/2] cxl/cli: enforce HPA-descending teardown order for destroy-region Pawel Mielimonka
2025-12-03 4:15 ` Alison Schofield
2025-12-03 10:13 ` Paweł Mielimonka
2025-12-03 23:46 ` Alison Schofield
2025-12-07 0:28 ` Alison Schofield
2025-12-03 3:38 ` [RFC PATCH v1 0/2] cxl/cli: HPA-ordered destroy-region teardown Alison Schofield
2026-01-20 14:32 ` [PATCH v2 0/1] " Pawel Mielimonka
2026-01-20 14:32 ` [PATCH v2 1/1] cxl/cli: enforce HPA-descening teardown order for destroy-region Pawel Mielimonka
2026-01-21 18:45 ` [PATCH v2 0/1] cxl/cli: HPA-ordered destroy-region teardown Alison Schofield
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=7eaf281d-6b92-4d8b-a633-e81925116364@gmail.com \
--to=pawel.mielimonka@gmail.com \
--cc=Smita.KoralahalliChannabasappa@amd.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=dave@stgolabs.net \
--cc=ira.weiny@intel.com \
--cc=jonathan.cameron@huawei.com \
--cc=linux-cxl@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pawel.mielimonka@fujitsu.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