From: Jonathan Cameron <Jonathan.Cameron@huawei.com>
To: Dave Jiang <dave.jiang@intel.com>
Cc: <linux-cxl@vger.kernel.org>,
Itaru Kitayama <itaru.kitayama@linux.dev>,
Dan Williams <dan.j.williams@intel.com>,
Marc Herbert <marc.herbert@linux.intel.com>,
Alison Schofield <alison.schofield@intel.com>,
<linuxarm@huawei.com>
Subject: Re: [PATCH] cxl_test: Limit location for fake CFMWS to mappable range
Date: Tue, 10 Jun 2025 10:17:10 +0100 [thread overview]
Message-ID: <20250610101710.000008b7@huawei.com> (raw)
In-Reply-To: <8b53e8e1-8b9f-4db5-952f-0a961942dfeb@intel.com>
On Mon, 9 Jun 2025 10:25:41 -0700
Dave Jiang <dave.jiang@intel.com> wrote:
> On 5/27/25 8:34 AM, Jonathan Cameron wrote:
> > Some architectures (e.g. arm64) only support memory hotplug operations on
> > a restricted set of physical addresses. This applies even when we are
> > faking some CXL fixed memory windows for the purposes of cxl_test.
> > That range can be queried with mhp_get_pluggable_range(true). Use the
> > minimum of that the top of that range and iomem_resource.end to establish
> > the 64GiB region used by cxl_test.
> >
> > From thread #2 which was related to the issue in #1.
> >
> > Link: https://lore.kernel.org/linux-cxl/20250522145622.00002633@huawei.com/ #2
> > Reported-by: Itaru Kitayama <itaru.kitayama@linux.dev>
> > Closes: https://github.com/pmem/ndctl/issues/278 #1
> > Reviewed-by: Dan Williams <dan.j.williams@intel.com>
> > Tested-by: Itaru Kitayama <itaru.kitayama@fujitsu.com <mailto:itaru.kitayama@fujitsu.com>
> > Tested-by: Marc Herbert <marc.herbert@linux.intel.com>
> > Signed-off-by: Jonathan Cameron <Jonathan.Cameron@huawei.com>
>
> Applied to cxl/next
>
> Added the config check from Alison
Thanks. Was about to send v2 but this is quicker ;)
>
> >
> > ---
> > I haven't given this a fixes tag because it never worked on arm64.
> > So it isn't a regression fix, and I'm not sure we want to back port this
> > which a fixes tag might well trigger. If people want one shout and I'll
> > try and figure out what is appropriate.
> > ---
> > tools/testing/cxl/test/cxl.c | 7 ++++++-
> > 1 file changed, 6 insertions(+), 1 deletion(-)
> >
> > diff --git a/tools/testing/cxl/test/cxl.c b/tools/testing/cxl/test/cxl.c
> > index 8a5815ca870d..6a25cca5636f 100644
> > --- a/tools/testing/cxl/test/cxl.c
> > +++ b/tools/testing/cxl/test/cxl.c
> > @@ -2,6 +2,7 @@
> > // Copyright(c) 2021 Intel Corporation. All rights reserved.
> >
> > #include <linux/platform_device.h>
> > +#include <linux/memory_hotplug.h>
> > #include <linux/genalloc.h>
> > #include <linux/module.h>
> > #include <linux/mutex.h>
> > @@ -1328,6 +1329,7 @@ static int cxl_mem_init(void)
> > static __init int cxl_test_init(void)
> > {
> > int rc, i;
> > + struct range mappable;
> >
> > cxl_acpi_test();
> > cxl_core_test();
> > @@ -1342,8 +1344,11 @@ static __init int cxl_test_init(void)
> > rc = -ENOMEM;
> > goto err_gen_pool_create;
> > }
> > + mappable = mhp_get_pluggable_range(true);
> >
> > - rc = gen_pool_add(cxl_mock_pool, iomem_resource.end + 1 - SZ_64G,
> > + rc = gen_pool_add(cxl_mock_pool,
> > + min(iomem_resource.end + 1 - SZ_64G,
> > + mappable.end + 1 - SZ_64G),
> > SZ_64G, NUMA_NO_NODE);
> > if (rc)
> > goto err_gen_pool_add;
>
>
next prev parent reply other threads:[~2025-06-10 9:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-27 15:34 [PATCH] cxl_test: Limit location for fake CFMWS to mappable range Jonathan Cameron
2025-05-27 19:31 ` Alison Schofield
2025-06-09 17:25 ` Dave Jiang
2025-06-10 9:17 ` Jonathan Cameron [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-06-10 0:02 Itaru Kitayama
2025-06-10 0:07 ` Dave Jiang
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=20250610101710.000008b7@huawei.com \
--to=jonathan.cameron@huawei.com \
--cc=alison.schofield@intel.com \
--cc=dan.j.williams@intel.com \
--cc=dave.jiang@intel.com \
--cc=itaru.kitayama@linux.dev \
--cc=linux-cxl@vger.kernel.org \
--cc=linuxarm@huawei.com \
--cc=marc.herbert@linux.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